Autorefresh is OFF

Tx hash: 2fadb72ed924601775a932c1ab20de9dec4e3ba3c97914db1bfdbb9c3061ded6

Tx prefix hash: 2fadb72ed924601775a932c1ab20de9dec4e3ba3c97914db1bfdbb9c3061ded6
Tx public key: 618b3656dbc7d757263877807fdbae7b57c0aacfce1f79896820cc65edeb705e
Timestamp: 1517424122 Timestamp [UCT]: 2018-01-31 18:42:02 Age [y:d:h:m:s]: 05:121:17:17:25
Block: 719 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1240 kB
Tx version: 1 No of confirmations: 1391288 RingCT/type: no
Extra: 01618b3656dbc7d757263877807fdbae7b57c0aacfce1f79896820cc65edeb705e0208000000006d6035b3

2 output(s) for total of 10000.00200000 TUBE

stealth address amount amount idx
00: aca0dfe4cf60de8cc87ac357fce2e2b217b79c8596342c294f2b2a2934f11075 0.00200000 96 of 58525
01: a0f7f21f40c5980c4685d3f91155ff5e9b0db6627acf9e1a9759c2064f5709f3 10000.00000000 756 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": 729, "vin": [ { "gen": { "height": 719 } } ], "vout": [ { "amount": 200000, "target": { "key": "aca0dfe4cf60de8cc87ac357fce2e2b217b79c8596342c294f2b2a2934f11075" } }, { "amount": 1000000000000, "target": { "key": "a0f7f21f40c5980c4685d3f91155ff5e9b0db6627acf9e1a9759c2064f5709f3" } } ], "extra": [ 1, 97, 139, 54, 86, 219, 199, 215, 87, 38, 56, 119, 128, 127, 219, 174, 123, 87, 192, 170, 207, 206, 31, 121, 137, 104, 32, 204, 101, 237, 235, 112, 94, 2, 8, 0, 0, 0, 0, 109, 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