Official PoolWebsiteGithub

Autorefresh is ON (10 s)

Tx hash: aff4eb1ea406a9539fbb5df0799e4fe91ca25d774ad0c9c7c7f3c6f523e3e6d2

Tx prefix hash: 173bb6f55df91a2adb77faacd40c5bbd9be0f5707e97fe89387f7864a0632801
Tx public key: f7882385d110dd1c891f1f415e5d213e81a33a7a6480736e08c55ac7468e9d4a
Timestamp: 1674622272 Timestamp [UCT]: 2023-01-25 04:51:12 Age [y:d:h:m:s]: 00:061:02:34:53
Block: 5204388 Fee (per_kB): 0.000000000 (0.000000000) Tx size: 0.1016 kB
Tx version: 2 No of confirmations: 348413 RingCT/type: yes/0
Extra: 01f7882385d110dd1c891f1f415e5d213e81a33a7a6480736e08c55ac7468e9d4a021100000001ce8d5103000000000000000000

1 output(s) for total of 7.011689869 TUBE

stealth address amount amount idx
00: 1d29ca44150e051fdb2a5011543df884c2221187bc557939b0270db86bbe90f3 7.011689869 19884909 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