Autorefresh is OFF

Tx hash: 9609c1e97eb70a70a964a52f1e7c078c82e15bc9beaff259723a88f0d557717b

Tx prefix hash: 9609c1e97eb70a70a964a52f1e7c078c82e15bc9beaff259723a88f0d557717b
Tx public key: 631d400ad60c050101048dc5cf4e12abf9f17bc019676efe149fc05c14894537
Timestamp: 1517407286 Timestamp [UCT]: 2018-01-31 14:01:26 Age [y:d:h:m:s]: 05:244:08:55:34
Block: 284 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1240 kB
Tx version: 1 No of confirmations: 1479577 RingCT/type: no
Extra: 01631d400ad60c050101048dc5cf4e12abf9f17bc019676efe149fc05c1489453702080000000066edfc57

2 output(s) for total of 10000.00200000 TUBE

stealth address amount amount idx
00: 4267c73477953363f99e7671b0de1a41654648969b573a07a7d8eb7eb991f21b 0.00200000 0 of 58525
01: 99c0418fccbcbd5350a43e620e9bf64ee78150f9ce7ec5428a0eae801af8af69 10000.00000000 299 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": 294, "vin": [ { "gen": { "height": 284 } } ], "vout": [ { "amount": 200000, "target": { "key": "4267c73477953363f99e7671b0de1a41654648969b573a07a7d8eb7eb991f21b" } }, { "amount": 1000000000000, "target": { "key": "99c0418fccbcbd5350a43e620e9bf64ee78150f9ce7ec5428a0eae801af8af69" } } ], "extra": [ 1, 99, 29, 64, 10, 214, 12, 5, 1, 1, 4, 141, 197, 207, 78, 18, 171, 249, 241, 123, 192, 25, 103, 110, 254, 20, 159, 192, 92, 20, 137, 69, 55, 2, 8, 0, 0, 0, 0, 102, 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