Monero-Classic Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Tx hash: dbcafa865380efb6f7818334382f58b5b955859a221d490655eb3b8efdde9202

Tx prefix hash: 034894a5208b7a40eba5b25683c5bc8ae165f3537a157099feef0ec0e6a8c7ce
Tx public key: 5c355b1b76b49a0b96f9cb4698dd42f5569fe6bc1b2116713830aed5cc9c93a9
Timestamp: 1539273730 Timestamp [UCT]: 2018-10-11 16:02:10 Age [y:d:h:m:s]: 00:063:16:03:20
Block: 1680810 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 44139 RingCT/type: yes/0
Extra: 015c355b1b76b49a0b96f9cb4698dd42f5569fe6bc1b2116713830aed5cc9c93a9020800004c5f8cb43996

1 output(s) for total of 3.749915397955 xmc

stealth address amount amount idx
00: ef121c88fb93e05d5d10b295b6eabb886b01b8100af2c821d6c901e37973f2e0 3.749915397955 5410768 of 0

Check which outputs belong to given Monero-Classic 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 Monero-Classic in this transaction

Tx private key can be obtained using get_tx_key command in monero-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": 2, "unlock_time": 1680870, "vin": [ { "gen": { "height": 1680810 } } ], "vout": [ { "amount": 3749915397955, "target": { "key": "ef121c88fb93e05d5d10b295b6eabb886b01b8100af2c821d6c901e37973f2e0" } } ], "extra": [ 1, 92, 53, 91, 27, 118, 180, 154, 11, 150, 249, 203, 70, 152, 221, 66, 245, 86, 159, 230, 188, 27, 33, 22, 113, 56, 48, 174, 213, 204, 156, 147, 169, 2, 8, 0, 0, 76, 95, 140, 180, 57, 150 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): HEAD-2018-04-07-06ebaa5 (1.0) | monero classic version: 0.11.1.0-release