Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c1eaf765519d61cdfee0df0234d3bb2d4a4d8bd9f32d0f862fe446742cc050f

Tx prefix hash: 1a0756da004798b06dd8e12744ca4b85915d21ca91d7358332ddff457e3741bd
Tx public key: 62bfa0e24f76d1d90dd408447d8fb5ada29183969cf0b71901e25dfda9dac159
Timestamp: 1773946531 Timestamp [UTC]: 2026-03-19 18:55:31 Age [y:d:h:m:s]: 00:240:10:10:00
Block: 1501400 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177254 RingCT/type: yes/0
Extra: 0162bfa0e24f76d1d90dd408447d8fb5ada29183969cf0b71901e25dfda9dac159021100000001f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 64fef84c8e8686a5ac83441c3ae12e4af8860dd5fd09962bc58acab57a429426 0.000600000000 1991084 of 15 -

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

Tx private key can be obtained using get_tx_key command in dinastycoin-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": 1501410, "vin": [ { "gen": { "height": 1501400 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64fef84c8e8686a5ac83441c3ae12e4af8860dd5fd09962bc58acab57a429426" } } ], "extra": [ 1, 98, 191, 160, 226, 79, 118, 209, 217, 13, 212, 8, 68, 125, 143, 181, 173, 162, 145, 131, 150, 156, 240, 183, 25, 1, 226, 93, 253, 169, 218, 193, 89, 2, 17, 0, 0, 0, 1, 241, 136, 200, 168, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: