Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 794df74ded4a38814806c9543e1e6d0256e6587f3ccc88e295a2f4dc2729b88d

Tx prefix hash: 065c409fcdce600e57fac926b2251aa9351dcd670e0288c5d9e44a3b85dda33f
Tx public key: dd400dc16125a63c1a8d31c483560c8e13230d0e4c7ab724907c1865c6c94697
Timestamp: 1764069239 Timestamp [UCT]: 2025-11-25 11:13:59 Age [y:d:h:m:s]: 00:001:23:01:40
Block: 1419786 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1402 RingCT/type: yes/0
Extra: 01dd400dc16125a63c1a8d31c483560c8e13230d0e4c7ab724907c1865c6c9469702110000000217b19132000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c1613fd9a6f720c7a95ef8126231f901d041bba12b1cae213070a8561a529d1 0.600000000000 1908327 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": 1419796, "vin": [ { "gen": { "height": 1419786 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c1613fd9a6f720c7a95ef8126231f901d041bba12b1cae213070a8561a529d1" } } ], "extra": [ 1, 221, 64, 13, 193, 97, 37, 166, 60, 26, 141, 49, 196, 131, 86, 12, 142, 19, 35, 13, 14, 76, 122, 183, 36, 144, 124, 24, 101, 198, 201, 70, 151, 2, 17, 0, 0, 0, 2, 23, 177, 145, 50, 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