Official PoolWebsiteGithub

Autorefresh is ON (10 s)

Tx hash: dc86ee67d3f0d70f666851f11596541ece61e2ef10a2e05ed1198c6c63683e3f

Tx prefix hash: f69b80e692cababc57fe10b64cf6ac1ff7a2bfe4c469065afa4fb6dd18099221
Tx public key: 14ded5e916fe8f2c76671c63bff757627ef8b6284850c47e1fd179f9b9d56067
Timestamp: 1641841967 Timestamp [UCT]: 2022-01-10 19:12:47 Age [y:d:h:m:s]: 00:137:16:13:33
Block: 3040116 Fee (per_kB): 0.000000000 (0.000000000) Tx size: 0.1016 kB
Tx version: 2 No of confirmations: 784998 RingCT/type: yes/0
Extra: 0114ded5e916fe8f2c76671c63bff757627ef8b6284850c47e1fd179f9b9d5606702110000000613ed5700000000000000000000

1 output(s) for total of 7.977277748 TUBE

stealth address amount amount idx
00: 01c6f70e0ee0c8ca287b20d330a92d8918ea2e4a0c6723c216e6eafb2123a9e4 7.977277748 14934701 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