Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66a9a4c01dba04a166e5a64b951bafcdcecb3e1ac563ab37f8dcebef21c2777c

Tx prefix hash: ed1f4746d5cb974c9945a2e4ec9a65700c8971de803e93f78de2fe29d5677a45
Tx public key: e38102fa91b814ba5f3edd63f0aa12b73e7b25caca129eb0e0e84c48905ac7f9
Timestamp: 1766225018 Timestamp [UCT]: 2025-12-20 10:03:38 Age [y:d:h:m:s]: 00:007:05:15:16
Block: 1437653 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 5159 RingCT/type: yes/0
Extra: 01e38102fa91b814ba5f3edd63f0aa12b73e7b25caca129eb0e0e84c48905ac7f90211000000027b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c4c6db7ed3f02c9140a535260801d285aa2d3e74750bbaaec28b38c024054a1a 0.600000000000 1926462 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": 1437663, "vin": [ { "gen": { "height": 1437653 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c4c6db7ed3f02c9140a535260801d285aa2d3e74750bbaaec28b38c024054a1a" } } ], "extra": [ 1, 227, 129, 2, 250, 145, 184, 20, 186, 95, 62, 221, 99, 240, 170, 18, 183, 62, 123, 37, 202, 202, 18, 158, 176, 224, 232, 76, 72, 144, 90, 199, 249, 2, 17, 0, 0, 0, 2, 123, 30, 81, 172, 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