Autorefresh is OFF

Tx hash: 307888058cc353c0c346b261350b16da68ccbf1d6ab35c741205cec00230d4f0

Tx prefix hash: 307888058cc353c0c346b261350b16da68ccbf1d6ab35c741205cec00230d4f0
Tx public key: 4e8fc7d1e221ab71b919f349d28e7c83070ae72a621eed55b717e5741aac84e1
Timestamp: 1517417413 Timestamp [UCT]: 2018-01-31 16:50:13 Age [y:d:h:m:s]: 04:156:22:33:42
Block: 572 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1240 kB
Tx version: 1 No of confirmations: 1154787 RingCT/type: no
Extra: 014e8fc7d1e221ab71b919f349d28e7c83070ae72a621eed55b717e5741aac84e1020800000003fbedfc57

2 output(s) for total of 10000.00100000 TUBE

stealth address amount amount idx
00: 3b70ae5b14c5322d3198293c881302b0f4707efe07f49a86cac3244aa45c5c42 0.00100000 151 of 60494
01: 45b5f7d1b584e682f2556bdef3ca43d956591a3f81b8b72001bf75afa41722aa 10000.00000000 604 of 3008

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



{ "version": 1, "unlock_time": 582, "vin": [ { "gen": { "height": 572 } } ], "vout": [ { "amount": 100000, "target": { "key": "3b70ae5b14c5322d3198293c881302b0f4707efe07f49a86cac3244aa45c5c42" } }, { "amount": 1000000000000, "target": { "key": "45b5f7d1b584e682f2556bdef3ca43d956591a3f81b8b72001bf75afa41722aa" } } ], "extra": [ 1, 78, 143, 199, 209, 226, 33, 171, 113, 185, 25, 243, 73, 210, 142, 124, 131, 7, 10, 231, 42, 98, 30, 237, 85, 183, 23, 229, 116, 26, 172, 132, 225, 2, 8, 0, 0, 0, 3, 251, 237, 252, 87 ], "signatures": [ ] }


Less details
source code | explorer version (api): master-2020-03-09-0f3cc6b (1.1) | bittube version: 3.1.0.0-master-34dd77663