Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eb1f646110455b331f56ae176affa179110fb9a729fffa07658ac823202ccd52

Tx prefix hash: 5cad2ef5967910736882c5e313a2cbe0132a0804e2758f5f5cdb8575d902c5b1
Tx public key: cda3e9233bb2d7d59b2c969ef993b60fb9a3ff81e46ed46f8af183b5a09a57d0
Timestamp: 1761852992 Timestamp [UCT]: 2025-10-30 19:36:32 Age [y:d:h:m:s]: 00:010:02:27:34
Block: 1401430 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7227 RingCT/type: yes/0
Extra: 01cda3e9233bb2d7d59b2c969ef993b60fb9a3ff81e46ed46f8af183b5a09a57d002110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4affefa1bce58166769f6b011433ae4a948c3592642f9d590088e2dade8149b3 0.600000000000 1889749 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": 1401440, "vin": [ { "gen": { "height": 1401430 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4affefa1bce58166769f6b011433ae4a948c3592642f9d590088e2dade8149b3" } } ], "extra": [ 1, 205, 163, 233, 35, 59, 178, 215, 213, 155, 44, 150, 158, 249, 147, 182, 15, 185, 163, 255, 129, 228, 110, 212, 111, 138, 241, 131, 181, 160, 154, 87, 208, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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