Autorefresh is OFF

Tx hash: 07202aff13216195dbfe961add931764293fcb0f821b4399194caaa6da410faf

Tx prefix hash: 07202aff13216195dbfe961add931764293fcb0f821b4399194caaa6da410faf
Tx public key: 53a8bff0bc1bc46c48da18615fd0d5699b13d5a318f1c9f58313befec3e2cf12
Timestamp: 1517406308 Timestamp [UCT]: 2018-01-31 13:45:08 Age [y:d:h:m:s]: 03:073:03:18:42
Block: 248 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1240 kB
Tx version: 1 No of confirmations: 838655 RingCT/type: no
Extra: 0153a8bff0bc1bc46c48da18615fd0d5699b13d5a318f1c9f58313befec3e2cf12020800000000069e1704

2 output(s) for total of 10000.00100000 TUBE

stealth address amount amount idx
00: 637824a8321b36b3404d8089cb6f33c624f9bb15fd573a28e11ad6a10d62263b 0.00100000 31 of 60494
01: dd197f11dcf1e53d6b961334b4bc8c9c7f32505788fe4cb4e8e9b2249e77e7fe 10000.00000000 262 of 3008

Check which outputs belong to given BitTube address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them BitTube in this transaction

Tx private key can be obtained using get_tx_key command in bittube-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 1, "unlock_time": 258, "vin": [ { "gen": { "height": 248 } } ], "vout": [ { "amount": 100000, "target": { "key": "637824a8321b36b3404d8089cb6f33c624f9bb15fd573a28e11ad6a10d62263b" } }, { "amount": 1000000000000, "target": { "key": "dd197f11dcf1e53d6b961334b4bc8c9c7f32505788fe4cb4e8e9b2249e77e7fe" } } ], "extra": [ 1, 83, 168, 191, 240, 188, 27, 196, 108, 72, 218, 24, 97, 95, 208, 213, 105, 155, 19, 213, 163, 24, 241, 201, 245, 131, 19, 190, 254, 195, 226, 207, 18, 2, 8, 0, 0, 0, 0, 6, 158, 23, 4 ], "signatures": [ ] }


Less details
source code | explorer version (api): master-2020-03-09-0f3cc6b (1.1) | bittube version: 3.1.0.0-master-34dd77663