Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 323ae87be3df1ba60311e3f448a1f8489979cd9367b3da953f0fb40d6c9a707a

Tx prefix hash: e9ad7911d8f0cb000218e92b257bf97749438141b20ca879fb9c8640a806abeb
Tx public key: 6ed101926e91dda3abcd2e523b822b0daf665a3739ce0372ab28b847d07cd1ea
Timestamp: 1763661472 Timestamp [UCT]: 2025-11-20 17:57:52 Age [y:d:h:m:s]: 00:032:16:41:15
Block: 1416401 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 23397 RingCT/type: yes/0
Extra: 016ed101926e91dda3abcd2e523b822b0daf665a3739ce0372ab28b847d07cd1ea02110000000170609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cb4723ebd861b1c2061b72f1d865d6e1c15307489703c186e012adb9b9d2214e 0.600000000000 1904920 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": 1416411, "vin": [ { "gen": { "height": 1416401 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cb4723ebd861b1c2061b72f1d865d6e1c15307489703c186e012adb9b9d2214e" } } ], "extra": [ 1, 110, 209, 1, 146, 110, 145, 221, 163, 171, 205, 46, 82, 59, 130, 43, 13, 175, 102, 90, 55, 57, 206, 3, 114, 171, 40, 184, 71, 208, 124, 209, 234, 2, 17, 0, 0, 0, 1, 112, 96, 157, 3, 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