Autorefresh is ON (10 s)

Tx hash: 64c3ed4b249e15e674820c1c908f35520304e6378d0c95e80bac0d4d8b815b3e

Tx prefix hash: 047a544b73ee004dc2030d2dedd3ed670f0f51acc75f2c9dcc07a06e9fbddd06
Tx public key: 1f704cf306a55a43bc98a7dc10e9aefb56d84e86e0a45ec382f35a0c350bb810
Timestamp: 1659726632 Timestamp [UCT]: 2022-08-05 19:10:32 Age [y:d:h:m:s]: 00:113:00:55:23
Block: 4220375 Fee (per_kB): 0.000000000 (0.000000000) Tx size: 0.1016 kB
Tx version: 2 No of confirmations: 644445 RingCT/type: yes/0
Extra: 011f704cf306a55a43bc98a7dc10e9aefb56d84e86e0a45ec382f35a0c350bb810021100000002255ad300000000000000000000

1 output(s) for total of 7.434951469 TUBE

stealth address amount amount idx
00: 67e7c7d55b71cd6a3fd3301ebdf5a3eb6ba9f09156189ee47d3b03f17b309e38 7.434951469 18100882 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: