Autorefresh is OFF

Tx hash: 0a94aa9b0c14ebdd87492ec6836af3bf9da8de9fb9b73fcac0ff3c81a3afd9c5

Tx prefix hash: 0a94aa9b0c14ebdd87492ec6836af3bf9da8de9fb9b73fcac0ff3c81a3afd9c5
Tx public key: 1e01bc03aa13991543f1a8837560508c1117e8af78e15276a74d5e14da1b8240
Timestamp: 1517451726 Timestamp [UCT]: 2018-02-01 02:22:06 Age [y:d:h:m:s]: 04:308:01:45:06
Block: 1196 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1240 kB
Tx version: 1 No of confirmations: 1262846 RingCT/type: no
Extra: 011e01bc03aa13991543f1a8837560508c1117e8af78e15276a74d5e14da1b8240020800000000246035b3

2 output(s) for total of 10000.00200000 TUBE

stealth address amount amount idx
00: a960ac09a67a26fd9371b522ba98144308b8cba86bbc05fd387b9fe77e56ebda 0.00200000 607 of 58525
01: 4fb41d048310ee8d514dd654fc2cbd16e1d180b5d83252786dc9558171518f67 10000.00000000 1234 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": 1206, "vin": [ { "gen": { "height": 1196 } } ], "vout": [ { "amount": 200000, "target": { "key": "a960ac09a67a26fd9371b522ba98144308b8cba86bbc05fd387b9fe77e56ebda" } }, { "amount": 1000000000000, "target": { "key": "4fb41d048310ee8d514dd654fc2cbd16e1d180b5d83252786dc9558171518f67" } } ], "extra": [ 1, 30, 1, 188, 3, 170, 19, 153, 21, 67, 241, 168, 131, 117, 96, 80, 140, 17, 23, 232, 175, 120, 225, 82, 118, 167, 77, 94, 20, 218, 27, 130, 64, 2, 8, 0, 0, 0, 0, 36, 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