Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de0fa546261aaae88ad5bf113c06bb00fa05bf6f5ed8ab81b150cbe8e518186c

Tx prefix hash: 554ddf2c5e8630b823adabe9d45b84fa2c31f3a58e036b74770bab36f39b04e8
Tx public key: 57923c4c8e47ca3eea6427d47492eea8d8bb8de078e9a6fd54747ef56534db6c
Timestamp: 1751383660 Timestamp [UCT]: 2025-07-01 15:27:40 Age [y:d:h:m:s]: 00:143:01:28:35
Block: 1316617 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100462 RingCT/type: yes/0
Extra: 0157923c4c8e47ca3eea6427d47492eea8d8bb8de078e9a6fd54747ef56534db6c021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d8b1b3a8e260fcdd7d096475eabd92d1e2f871a18458829abfbd9d780470acdf 0.600000000000 1804278 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": 1316627, "vin": [ { "gen": { "height": 1316617 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d8b1b3a8e260fcdd7d096475eabd92d1e2f871a18458829abfbd9d780470acdf" } } ], "extra": [ 1, 87, 146, 60, 76, 142, 71, 202, 62, 234, 100, 39, 212, 116, 146, 238, 168, 216, 187, 141, 224, 120, 233, 166, 253, 84, 116, 126, 245, 101, 52, 219, 108, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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