Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0df41eca6218cd07be605e86f4921a4cb44dae57065acb1df2e0288eb5b6401d

Tx prefix hash: 6c5ad6dedb13bd95a43bc8935944092d416b13dd891be97eb9e06a7075673fde
Tx public key: 62d861a3b4c96ec1b74c7aff40f3c9d32a268cf91dfbc4468c0409bdb66c5eff
Timestamp: 1753375521 Timestamp [UCT]: 2025-07-24 16:45:21 Age [y:d:h:m:s]: 00:166:13:44:38
Block: 1332491 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117940 RingCT/type: yes/0
Extra: 0162d861a3b4c96ec1b74c7aff40f3c9d32a268cf91dfbc4468c0409bdb66c5eff021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 00adfd1610144d4c0d9c19c144d61a5ef4bc82397d63b31e4678becc22746347 0.600000000000 1820288 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": 1332501, "vin": [ { "gen": { "height": 1332491 } } ], "vout": [ { "amount": 600000000, "target": { "key": "00adfd1610144d4c0d9c19c144d61a5ef4bc82397d63b31e4678becc22746347" } } ], "extra": [ 1, 98, 216, 97, 163, 180, 201, 110, 193, 183, 76, 122, 255, 64, 243, 201, 211, 42, 38, 140, 249, 29, 251, 196, 70, 140, 4, 9, 189, 182, 108, 94, 255, 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