Official PoolWebsiteGithub

Autorefresh is ON (10 s)

Tx hash: 5a2eaac0a640924a5e420c3e9e57e4c1f7809c358087e1a81606bed2568cb0f7

Tx prefix hash: 5b0ea8f5660be475dad329d980383f3b9e8a3ed0bcf89c0bae222b607b01c684
Tx public key: cd6183d6cbb8273a1cb0bd6d7b2938805cd96967a01a820d2d02f0e0a8e93101
Timestamp: 1679220220 Timestamp [UCT]: 2023-03-19 10:03:40 Age [y:d:h:m:s]: 00:070:09:50:44
Block: 5507732 Fee (per_kB): 0.000000000 (0.000000000) Tx size: 0.1016 kB
Tx version: 2 No of confirmations: 397771 RingCT/type: yes/0
Extra: 01cd6183d6cbb8273a1cb0bd6d7b2938805cd96967a01a820d2d02f0e0a8e9310102110000000242201f03000000000000000000

1 output(s) for total of 6.885786952 TUBE

stealth address amount amount idx
00: bd4c8b9942d7d161b96d749ab02ea346ba1bdc8acb6ffc56362d7be09fd2b2f6 6.885786952 20242025 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