Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d527c21b276a065ba992c1f19546b1a72a593a0517ffd09f70370ef468f90b4b

Tx prefix hash: e57e0b23754fbe31c5dfbefa9335ed724f701a8b27d735750ae01c930834263f
Tx public key: 1fd17c2defa02bfadeb8406d9eac74a1173a63288e3a372be18b91a0e60b0fac
Timestamp: 1764155525 Timestamp [UCT]: 2025-11-26 11:12:05 Age [y:d:h:m:s]: 00:000:02:10:18
Block: 1420497 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66 RingCT/type: yes/0
Extra: 011fd17c2defa02bfadeb8406d9eac74a1173a63288e3a372be18b91a0e60b0fac021100000001d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cb15c9d8c349bcf1f3e3fc7ef8f4f9b106072ff90d606b0631fc60d86d94b3af 0.600000000000 1909040 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": 1420507, "vin": [ { "gen": { "height": 1420497 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cb15c9d8c349bcf1f3e3fc7ef8f4f9b106072ff90d606b0631fc60d86d94b3af" } } ], "extra": [ 1, 31, 209, 124, 45, 239, 160, 43, 250, 222, 184, 64, 109, 158, 172, 116, 161, 23, 58, 99, 40, 142, 58, 55, 43, 225, 139, 145, 160, 230, 11, 15, 172, 2, 17, 0, 0, 0, 1, 214, 225, 157, 124, 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