Autorefresh is OFF

Tx hash: 9844e52aa8f5e83ab52e3a60be87c3fc547e93d04010d0927fd524f7d287e39c

Tx prefix hash: 9844e52aa8f5e83ab52e3a60be87c3fc547e93d04010d0927fd524f7d287e39c
Tx public key: dbded6377a27d99d18daed33f96eb43ace7bf0cc2c83d3d4517304fecbdea71a
Timestamp: 1517411707 Timestamp [UCT]: 2018-01-31 15:15:07 Age [y:d:h:m:s]: 04:156:09:55:47
Block: 426 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1240 kB
Tx version: 1 No of confirmations: 1154492 RingCT/type: no
Extra: 01dbded6377a27d99d18daed33f96eb43ace7bf0cc2c83d3d4517304fecbdea71a020800000000390b68b0

2 output(s) for total of 10000.00100000 TUBE

stealth address amount amount idx
00: 6b117c8812776b4eb643dc03a48bd121dc0f12eb04ea7f2b253f55524936cfa2 0.00100000 86 of 60494
01: e112d7d82dd9808de0acb8cdbc95b3d567f252cca98116aefe85370ed0d7bc0f 10000.00000000 442 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": 436, "vin": [ { "gen": { "height": 426 } } ], "vout": [ { "amount": 100000, "target": { "key": "6b117c8812776b4eb643dc03a48bd121dc0f12eb04ea7f2b253f55524936cfa2" } }, { "amount": 1000000000000, "target": { "key": "e112d7d82dd9808de0acb8cdbc95b3d567f252cca98116aefe85370ed0d7bc0f" } } ], "extra": [ 1, 219, 222, 214, 55, 122, 39, 217, 157, 24, 218, 237, 51, 249, 110, 180, 58, 206, 123, 240, 204, 44, 131, 211, 212, 81, 115, 4, 254, 203, 222, 167, 26, 2, 8, 0, 0, 0, 0, 57, 11, 104, 176 ], "signatures": [ ] }


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