Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd58263a33955b81591d28874ab9def54daea8355a3daa0105b66647c031336a

Tx prefix hash: 57dd0999e6ba7591362f39c728c871c54321916930cc024df8da9fad7aed3c26
Tx public key: de217757d5f60b3243f8f942fe8f360df5542638aaf353b5f6e42d4a9834a0c1
Timestamp: 1752089893 Timestamp [UCT]: 2025-07-09 19:38:13 Age [y:d:h:m:s]: 00:128:05:18:30
Block: 1322134 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 90183 RingCT/type: yes/0
Extra: 01de217757d5f60b3243f8f942fe8f360df5542638aaf353b5f6e42d4a9834a0c10211000000048368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 602325c320cac63b3bb08cfa24855aa4683535d1e566794338e6aa45e42951d6 0.600000000000 1809847 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": 1322144, "vin": [ { "gen": { "height": 1322134 } } ], "vout": [ { "amount": 600000000, "target": { "key": "602325c320cac63b3bb08cfa24855aa4683535d1e566794338e6aa45e42951d6" } } ], "extra": [ 1, 222, 33, 119, 87, 213, 246, 11, 50, 67, 248, 249, 66, 254, 143, 54, 13, 245, 84, 38, 56, 170, 243, 83, 181, 246, 228, 45, 74, 152, 52, 160, 193, 2, 17, 0, 0, 0, 4, 131, 104, 38, 109, 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