Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 376f09ffe03910247ceea83c4b05f1dfd5e965d2af5b7f8d7774453a4161c655

Tx prefix hash: bbbc34821fd184e4758fb6f74a0ca178f1f09b4a086fe1763cf0b5566742dfbb
Tx public key: d37c9dd4c4ff5912f7e07509e6370b9618c228bd127f99811adbb1b7e6cb1741
Timestamp: 1761057671 Timestamp [UCT]: 2025-10-21 14:41:11 Age [y:d:h:m:s]: 00:070:15:26:22
Block: 1394842 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 50561 RingCT/type: yes/0
Extra: 01d37c9dd4c4ff5912f7e07509e6370b9618c228bd127f99811adbb1b7e6cb1741021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5c264fe1a313f522b67b69fc15274e2306c4ba9d68a831bb523a30e0e68d7454 0.600000000000 1883117 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": 1394852, "vin": [ { "gen": { "height": 1394842 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c264fe1a313f522b67b69fc15274e2306c4ba9d68a831bb523a30e0e68d7454" } } ], "extra": [ 1, 211, 124, 157, 212, 196, 255, 89, 18, 247, 224, 117, 9, 230, 55, 11, 150, 24, 194, 40, 189, 18, 127, 153, 129, 26, 219, 177, 183, 230, 203, 23, 65, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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