Official PoolWebsiteGithub

Autorefresh is ON (10 s)

Tx hash: abe7b9d194753ab7b2a895524dc63a68bd9a7b20e873a217039886e864723d6b

Tx prefix hash: fe6d5526ea56f5259d972fcb257e8536f91c9df5f037d1869ea491ae11a6f132
Tx public key: 20ed0dc32d9c3beafdf439645614642bcc8a10f7a45cb8d78ff25c23b7ec3cdc
Timestamp: 1622153391 Timestamp [UCT]: 2021-05-27 22:09:51 Age [y:d:h:m:s]: 01:000:12:30:38
Block: 1735238 Fee (per_kB): 0.000000000 (0.000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2089684 RingCT/type: yes/0
Extra: 0120ed0dc32d9c3beafdf439645614642bcc8a10f7a45cb8d78ff25c23b7ec3cdc02110000000168586300000000000000000000

1 output(s) for total of 8.621962455 TUBE

stealth address amount amount idx
00: 384e9c51b6a36021ac029058b6724488e97b48ed7d3afd3701bb4b6751386069 8.621962455 8972013 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