Official PoolWebsiteGithub

Autorefresh is ON (10 s)

Tx hash: 1e1beed8a801998ad83be2acbf13d37be2732ee3b9b5c0d65ed4ff193e140026

Tx prefix hash: af3abc41607d239097550bd8fd746fd62a7116499932aae096a36537810d5e5a
Tx public key: 2b6256cdb97c4fcb032f3c43f15f290a4c652286a08445efa40a6925a77957b1
Timestamp: 1674621790 Timestamp [UCT]: 2023-01-25 04:43:10 Age [y:d:h:m:s]: 00:054:08:12:20
Block: 5204358 Fee (per_kB): 0.000000000 (0.000000000) Tx size: 0.1016 kB
Tx version: 2 No of confirmations: 309780 RingCT/type: yes/0
Extra: 012b6256cdb97c4fcb032f3c43f15f290a4c652286a08445efa40a6925a77957b1021100000001ce8d5103000000000000000000

1 output(s) for total of 7.011429058 TUBE

stealth address amount amount idx
00: 4b2950f7d734b8f02dd1f2d1c5cc54c1d8969cdf031c624f1e052d7cd5463dd2 7.011429058 19884879 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