Official PoolWebsiteGithub

Autorefresh is ON (10 s)

Tx hash: 320f8ff7bd6f3a5d58435cad820162fe73a7e5bdd95c13bae52d3c8c8310a9b3

Tx prefix hash: c5f2f269b034685c4bcdce563dccc36007117618de2c3b3e8ae5f2325a14009b
Tx public key: cd31780ada3639d51a08a96106e530e15a2ce0ff4a02006af5e3edb0caf7cfcf
Timestamp: 1637796982 Timestamp [UCT]: 2021-11-24 23:36:22 Age [y:d:h:m:s]: 00:184:11:06:50
Block: 2772080 Fee (per_kB): 0.000000000 (0.000000000) Tx size: 0.1016 kB
Tx version: 2 No of confirmations: 1052845 RingCT/type: yes/0
Extra: 01cd31780ada3639d51a08a96106e530e15a2ce0ff4a02006af5e3edb0caf7cfcf0211000000031b335900000000000000000000

1 output(s) for total of 8.105260493 TUBE

stealth address amount amount idx
00: 4bbfb37ef8a99a5299106580160ce1caf57b0286084ab0bfb40a7df8be8146bc 8.105260493 13827022 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