Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 571dd90e80f138aea5ffa4dc16e78fe9e3fdc7f2605b8fadf256061ba900bbc3

Tx prefix hash: 20cab5c1fd34a6e88ee0a69d270abb930b4fb891fc0c008c0de4990455096fe4
Tx public key: 05216c3a0eb7e7e29aa4387c7eb802697886d7d17ff11f4798ccb842c10db371
Timestamp: 1765911312 Timestamp [UCT]: 2025-12-16 18:55:12 Age [y:d:h:m:s]: 00:012:02:28:14
Block: 1435040 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8674 RingCT/type: yes/0
Extra: 0105216c3a0eb7e7e29aa4387c7eb802697886d7d17ff11f4798ccb842c10db371021100000005d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cfee4a345f99847d3c7927d4bdaa8dc8d211cd4658d463cea9701e6f69bd72ac 0.600000000000 1923837 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": 1435050, "vin": [ { "gen": { "height": 1435040 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cfee4a345f99847d3c7927d4bdaa8dc8d211cd4658d463cea9701e6f69bd72ac" } } ], "extra": [ 1, 5, 33, 108, 58, 14, 183, 231, 226, 154, 164, 56, 124, 126, 184, 2, 105, 120, 134, 215, 209, 127, 241, 31, 71, 152, 204, 184, 66, 193, 13, 179, 113, 2, 17, 0, 0, 0, 5, 214, 225, 157, 124, 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