Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e52dabc81c51371121e668d897ba5970299aa65a58c0d71fd8a90d5a04a1f722

Tx prefix hash: 1f1c6468cc463e832ca76652fe98bc3afc4c97c661a46d96cfd468525495376f
Tx public key: 4de8069f505b0e3e42582920a30818529bd6cda13c5a80fd2282aa41ca28e45f
Timestamp: 1759266363 Timestamp [UCT]: 2025-09-30 21:06:03 Age [y:d:h:m:s]: 00:040:03:20:32
Block: 1379968 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 28752 RingCT/type: yes/0
Extra: 014de8069f505b0e3e42582920a30818529bd6cda13c5a80fd2282aa41ca28e45f021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f60dc0c7c49cff93250823cc17e51e05a407706cd0f69dab73241fae833fab8d 0.600000000000 1868079 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": 1379978, "vin": [ { "gen": { "height": 1379968 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f60dc0c7c49cff93250823cc17e51e05a407706cd0f69dab73241fae833fab8d" } } ], "extra": [ 1, 77, 232, 6, 159, 80, 91, 14, 62, 66, 88, 41, 32, 163, 8, 24, 82, 155, 214, 205, 161, 60, 90, 128, 253, 34, 130, 170, 65, 202, 40, 228, 95, 2, 17, 0, 0, 0, 2, 216, 231, 210, 65, 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