Official PoolWebsiteGithub

Autorefresh is ON (10 s)

Tx hash: 3c8d8f37379257e3f56d21f9ba36e3d2b6205ce664734885a8d5d91c76193b63

Tx prefix hash: 7b8f2a22dadc8426a844336e8759c4aac482e9d9c6f447231512df07aa5e95ac
Tx public key: aa06b8c31f39be7730c9ef1118b9948daf26658ceb0b4476452fa1a4717fd8e2
Timestamp: 1656016482 Timestamp [UCT]: 2022-06-23 20:34:42 Age [y:d:h:m:s]: 00:053:21:48:15
Block: 3975863 Fee (per_kB): 0.000000000 (0.000000000) Tx size: 0.1016 kB
Tx version: 2 No of confirmations: 306634 RingCT/type: yes/0
Extra: 01aa06b8c31f39be7730c9ef1118b9948daf26658ceb0b4476452fa1a4717fd8e2021100000001255ad300000000000000000000

1 output(s) for total of 7.544059315 TUBE

stealth address amount amount idx
00: 993be3ebc55733acad85d076bf90031aee7264fa164a4230e3c61680c5599f7c 7.544059315 17613026 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