Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da2a170816c128030d786cc64c7e8d1a4b7e4fa0a3d2729d82d5322d577e2fa0

Tx prefix hash: 59ecaf9591d56ba63bc0f5ecb4e178d47a41777428a9cde9c2ccb4b1ca6e43bb
Tx public key: 3c0985ad19c5cd6738ebcab65ec8b5cc7f65ec09d04df4fa552087f8efd18353
Timestamp: 1759914189 Timestamp [UCT]: 2025-10-08 09:03:09 Age [y:d:h:m:s]: 00:074:22:53:33
Block: 1385337 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 53674 RingCT/type: yes/0
Extra: 013c0985ad19c5cd6738ebcab65ec8b5cc7f65ec09d04df4fa552087f8efd1835302110000000197baf922000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: af5397e83c76c80019e4cf7a44d7ae545e3e4fa687685be399d2eed229dc5e7d 0.600000000000 1873500 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": 1385347, "vin": [ { "gen": { "height": 1385337 } } ], "vout": [ { "amount": 600000000, "target": { "key": "af5397e83c76c80019e4cf7a44d7ae545e3e4fa687685be399d2eed229dc5e7d" } } ], "extra": [ 1, 60, 9, 133, 173, 25, 197, 205, 103, 56, 235, 202, 182, 94, 200, 181, 204, 127, 101, 236, 9, 208, 77, 244, 250, 85, 32, 135, 248, 239, 209, 131, 83, 2, 17, 0, 0, 0, 1, 151, 186, 249, 34, 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