Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c687e7b03329910a4094cefc9852bba1a717ff31a2fbb1cbe93d4303c752e28a

Tx prefix hash: 23d63f988761d78605e2ba608a89fa13dd741376ec6d676e7f7bf9dce87f97b2
Tx public key: eda53f6dfae5fcd27618c706531561a065d45cf1720ddc91f6d0a1cec5061216
Timestamp: 1762388453 Timestamp [UCT]: 2025-11-06 00:20:53 Age [y:d:h:m:s]: 00:047:22:01:18
Block: 1405840 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 34311 RingCT/type: yes/0
Extra: 01eda53f6dfae5fcd27618c706531561a065d45cf1720ddc91f6d0a1cec50612160211000000055dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6ccd30826d7e901bd125e3b625ebe2e3ed5cff3abecc27ac0f8134f8d2fae581 0.600000000000 1894221 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": 1405850, "vin": [ { "gen": { "height": 1405840 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ccd30826d7e901bd125e3b625ebe2e3ed5cff3abecc27ac0f8134f8d2fae581" } } ], "extra": [ 1, 237, 165, 63, 109, 250, 229, 252, 210, 118, 24, 199, 6, 83, 21, 97, 160, 101, 212, 92, 241, 114, 13, 220, 145, 246, 208, 161, 206, 197, 6, 18, 22, 2, 17, 0, 0, 0, 5, 93, 251, 190, 42, 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