Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0df91e8b6e57692a35ee5c3c4b81471382a6da669ba5cb6d5060ad2ed4622a78

Tx prefix hash: ea9e0ab9b465b3eafcb44f2923e107fcc1333835d86ad1b385ca341e86327ee2
Tx public key: eab6e7dc2649d7145332a29cb23cf8fc43a9f860a35901d99166d6ef69260e27
Timestamp: 1752360465 Timestamp [UCT]: 2025-07-12 22:47:45 Age [y:d:h:m:s]: 00:179:20:54:44
Block: 1324201 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127349 RingCT/type: yes/0
Extra: 01eab6e7dc2649d7145332a29cb23cf8fc43a9f860a35901d99166d6ef69260e2702110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 94f0ab5495eb131d0c99e206c847a8c6d482353e8dc0aad0c46f277d8fe976aa 0.600000000000 1811944 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": 1324211, "vin": [ { "gen": { "height": 1324201 } } ], "vout": [ { "amount": 600000000, "target": { "key": "94f0ab5495eb131d0c99e206c847a8c6d482353e8dc0aad0c46f277d8fe976aa" } } ], "extra": [ 1, 234, 182, 231, 220, 38, 73, 215, 20, 83, 50, 162, 156, 178, 60, 248, 252, 67, 169, 248, 96, 163, 89, 1, 217, 145, 102, 214, 239, 105, 38, 14, 39, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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