Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e1df95610442379c775aa049adc02cb7d9b3314e720d94f598287307deae7fc

Tx prefix hash: b61d35ad85df94db3f8ef58447dd521cc441b87c4d04132ed2a20427a466c4ea
Tx public key: 0719abd90e6b0096d6099d711cefcc65b18045dc92ec45f82e0dab1a2beb0eab
Timestamp: 1764083120 Timestamp [UCT]: 2025-11-25 15:05:20 Age [y:d:h:m:s]: 00:001:16:52:55
Block: 1419895 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1224 RingCT/type: yes/0
Extra: 010719abd90e6b0096d6099d711cefcc65b18045dc92ec45f82e0dab1a2beb0eab021100000001fb8fd089000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c7239e2f1f719ca938a7ccb21c28b869ec29f62781ac67fdd0a7648ce267bcc4 0.600000000000 1908436 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 dinasty-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": 1419905, "vin": [ { "gen": { "height": 1419895 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c7239e2f1f719ca938a7ccb21c28b869ec29f62781ac67fdd0a7648ce267bcc4" } } ], "extra": [ 1, 7, 25, 171, 217, 14, 107, 0, 150, 214, 9, 157, 113, 28, 239, 204, 101, 177, 128, 69, 220, 146, 236, 69, 248, 46, 13, 171, 26, 43, 235, 14, 171, 2, 17, 0, 0, 0, 1, 251, 143, 208, 137, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8