Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c9f557d0e2b3b6cf419c0ecf252a28a2343edd0a573062bc42144ae29a89156f

Tx prefix hash: 078074e2d9e203fc8804534216227ab2570b19c8855517dea47e24d8c09672e7
Tx public key: 8d9ad20eb24e6105d6d0d98f06a1acc2482f0cf2b460d631f09e12894b4d98db
Timestamp: 1751355131 Timestamp [UCT]: 2025-07-01 07:32:11 Age [y:d:h:m:s]: 00:136:01:20:15
Block: 1316390 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95450 RingCT/type: yes/0
Extra: 018d9ad20eb24e6105d6d0d98f06a1acc2482f0cf2b460d631f09e12894b4d98db02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2506d67bd0305416e11a31ae915df67ce509d1833e702ec556c056f3ba856d6c 0.600000000000 1804049 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": 1316400, "vin": [ { "gen": { "height": 1316390 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2506d67bd0305416e11a31ae915df67ce509d1833e702ec556c056f3ba856d6c" } } ], "extra": [ 1, 141, 154, 210, 14, 178, 78, 97, 5, 214, 208, 217, 143, 6, 161, 172, 194, 72, 47, 12, 242, 180, 96, 214, 49, 240, 158, 18, 137, 75, 77, 152, 219, 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