Official PoolWebsiteGithub

Autorefresh is ON (10 s)

Tx hash: 0e9e9821ccb0f988bb19c80caed5d62bc30a05cde0f7434db57af7230337d1f3

Tx prefix hash: 1b532d2b733f26440c488ce7732e21e3b8b0665ddc24f0a301f84e33c8e689d2
Tx public key: 190560f994ab3b073e708e0298bf6cb9b2790b67df4a49c4c4085e4095d3afd3
Timestamp: 1674623111 Timestamp [UCT]: 2023-01-25 05:05:11 Age [y:d:h:m:s]: 00:061:02:58:46
Block: 5204447 Fee (per_kB): 0.000000000 (0.000000000) Tx size: 0.1016 kB
Tx version: 2 No of confirmations: 348475 RingCT/type: yes/0
Extra: 01190560f994ab3b073e708e0298bf6cb9b2790b67df4a49c4c4085e4095d3afd3021100000001ce8d5103000000000000000000

1 output(s) for total of 7.011360311 TUBE

stealth address amount amount idx
00: f013e14f869e281acee31581036c5df68f7b794280415515a20458f95e87c8fa 7.011360311 19884976 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