Monero-Classic Blockchain Explorer

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

Tx hash: ffe8076a10c8e711e9a39f6515b63fa5e6f3eda5b695e983ba6beeb9a4d8c01a

Tx prefix hash: 8cf2ada6e128608855595efb317ff27b484dcb0a818cdc9668fb5ed091425a10
Tx public key: dd3ff431ee7702269a2d671b1010c963e3d480f3a91db827938526d2f1b33077
Timestamp: 1539274076 Timestamp [UCT]: 2018-10-11 16:07:56 Age [y:d:h:m:s]: 00:063:16:14:18
Block: 1680812 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 44144 RingCT/type: yes/0
Extra: 01dd3ff431ee7702269a2d671b1010c963e3d480f3a91db827938526d2f1b33077020800a093011f500100

1 output(s) for total of 3.749901093176 xmc

stealth address amount amount idx
00: 661702d79d3916ff2f7905585379a5aa7dbc59e7ee8c101166822cbd85f4a208 3.749901093176 5410776 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": 1680872, "vin": [ { "gen": { "height": 1680812 } } ], "vout": [ { "amount": 3749901093176, "target": { "key": "661702d79d3916ff2f7905585379a5aa7dbc59e7ee8c101166822cbd85f4a208" } } ], "extra": [ 1, 221, 63, 244, 49, 238, 119, 2, 38, 154, 45, 103, 27, 16, 16, 201, 99, 227, 212, 128, 243, 169, 29, 184, 39, 147, 133, 38, 210, 241, 179, 48, 119, 2, 8, 0, 160, 147, 1, 31, 80, 1, 0 ], "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