Autorefresh is OFF

Tx hash: 40b4ae2a4fe01391c222e03749549692418f085551dc3eed7209c2faed3d8fb0

Tx prefix hash: 40b4ae2a4fe01391c222e03749549692418f085551dc3eed7209c2faed3d8fb0
Tx public key: 9a2992f7e5808b30ff41396c0913f063d25a16d30cba03ec4e351365134ea3c9
Timestamp: 1517450294 Timestamp [UCT]: 2018-02-01 01:58:14 Age [y:d:h:m:s]: 05:244:13:26:16
Block: 1183 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1240 kB
Tx version: 1 No of confirmations: 1479166 RingCT/type: no
Extra: 019a2992f7e5808b30ff41396c0913f063d25a16d30cba03ec4e351365134ea3c9020800000001156035b3

2 output(s) for total of 10000.00200000 TUBE

stealth address amount amount idx
00: fe99c201a20f83ff2f0007968fd7659d2b74ab6e4064c2b5072f2afa53a5c4f3 0.00200000 591 of 58525
01: 353da273183e71bcfd41cef8954f7533133700b471472e3aae17b84d39c8e590 10000.00000000 1221 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": 1193, "vin": [ { "gen": { "height": 1183 } } ], "vout": [ { "amount": 200000, "target": { "key": "fe99c201a20f83ff2f0007968fd7659d2b74ab6e4064c2b5072f2afa53a5c4f3" } }, { "amount": 1000000000000, "target": { "key": "353da273183e71bcfd41cef8954f7533133700b471472e3aae17b84d39c8e590" } } ], "extra": [ 1, 154, 41, 146, 247, 229, 128, 139, 48, 255, 65, 57, 108, 9, 19, 240, 99, 210, 90, 22, 211, 12, 186, 3, 236, 78, 53, 19, 101, 19, 78, 163, 201, 2, 8, 0, 0, 0, 1, 21, 96, 53, 179 ], "signatures": [ ] }


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