Autorefresh is ON (10 s)

Tx hash: b9f31eb20eb70e93f84ab6c7f6136f125459b3f3c83b3ea37628df0a84d53272

Tx prefix hash: 6baf1f41449c2d65346bc24687d84935d87627b5f9bc171518e4b9555991af7b
Tx public key: 7db4c8b1d8bad846410f460ae530f30fbc3b292d5c4438f7471d8767a12a87f4
Timestamp: 1654181160 Timestamp [UCT]: 2022-06-02 14:46:00 Age [y:d:h:m:s]: 00:114:20:14:44
Block: 3854572 Fee (per_kB): 0.000000000 (0.000000000) Tx size: 0.1016 kB
Tx version: 2 No of confirmations: 653519 RingCT/type: yes/0
Extra: 017db4c8b1d8bad846410f460ae530f30fbc3b292d5c4438f7471d8767a12a87f402110000000a0f59d200000000000000000000

1 output(s) for total of 7.598830610 TUBE

stealth address amount amount idx
00: 399099a7bc251a743255f4f81d1fb0bb0af661f77a0462359911d3190a7b92a7 7.598830610 17385871 of 0

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



More details
explorer version (api): master-2020-07-27-18a708f (1.1) | bittube version: 4.0.0.0-14d7aef36