Official PoolWebsiteGithub

Autorefresh is ON (10 s)

Tx hash: b31cd0f89e2b0a135631ce3aaf96f7378387dd55f1312826bd122ba94d20c990

Tx prefix hash: b8c4bf03bb1be9281ce7a3a9ef78d8f08ddd531b392ace0b4e62eaf9afb814c7
Tx public key: 53e0db86e6df42b6814954715fd9ae68fb5b11400a373a013b172f06cb47e868
Timestamp: 1659752936 Timestamp [UCT]: 2022-08-06 02:28:56 Age [y:d:h:m:s]: 00:010:16:56:40
Block: 4222179 Fee (per_kB): 0.000000000 (0.000000000) Tx size: 0.1016 kB
Tx version: 2 No of confirmations: 60396 RingCT/type: yes/0
Extra: 0153e0db86e6df42b6814954715fd9ae68fb5b11400a373a013b172f06cb47e868021100000001563a3800000000000000000000

1 output(s) for total of 7.434126354 TUBE

stealth address amount amount idx
00: 7fd6896c2f076d77b3b909c00e995121a367b87143a006c188f0ad0a009a4522 7.434126354 18103157 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