Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c20f049803b0e7970d8cf1868c7fbe05fbadea6f49014dac0aa41df173f200c7

Tx prefix hash: f014b0a4043d6e7430b069bef1aa9bbc10a56967fa5713ceceb0ecf207b7f90f
Tx public key: 4821a84d8882152a590aafaea9fc5fc6349dcb6d686bf8f70f5fcf35d65a4257
Timestamp: 1759979853 Timestamp [UCT]: 2025-10-09 03:17:33 Age [y:d:h:m:s]: 00:114:01:52:49
Block: 1385894 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81496 RingCT/type: yes/0
Extra: 014821a84d8882152a590aafaea9fc5fc6349dcb6d686bf8f70f5fcf35d65a4257021100000005a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: db36a650ad5ae0fa43b751841c5f77d780ad2cdad8b7071f01067e0f57850891 0.600000000000 1874057 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": 1385904, "vin": [ { "gen": { "height": 1385894 } } ], "vout": [ { "amount": 600000000, "target": { "key": "db36a650ad5ae0fa43b751841c5f77d780ad2cdad8b7071f01067e0f57850891" } } ], "extra": [ 1, 72, 33, 168, 77, 136, 130, 21, 42, 89, 10, 175, 174, 169, 252, 95, 198, 52, 157, 203, 109, 104, 107, 248, 247, 15, 95, 207, 53, 214, 90, 66, 87, 2, 17, 0, 0, 0, 5, 165, 220, 205, 121, 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