Official PoolWebsiteGithub

Autorefresh is ON (10 s)

Tx hash: a1b556ed13f7c39e1f71aa97c548fe50f2b0b25e9f6ab4a046864b20aeff328c

Tx prefix hash: 381324ed5fb9ef47937a4774c3de5206544c468e9c56992c8c52b980e93192e9
Tx public key: f2d384c924a3088fdf255ac8058f11cbc8eb79846d0c24c3e86af0f6af33b0e8
Timestamp: 1642194672 Timestamp [UCT]: 2022-01-14 21:11:12 Age [y:d:h:m:s]: 00:211:03:19:48
Block: 3063479 Fee (per_kB): 0.000000000 (0.000000000) Tx size: 0.0830 kB
Tx version: 2 No of confirmations: 1203354 RingCT/type: yes/0
Extra: 01f2d384c924a3088fdf255ac8058f11cbc8eb79846d0c24c3e86af0f6af33b0e8

1 output(s) for total of 7.965706910 TUBE

stealth address amount amount idx
00: f270eb4d04f9a0f41c991e5bc5ff9b40a83f92fe06acf37f07d3245d5376eab0 7.965706910 15018401 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