Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73c2555e2ea779eebdaca1be97a4a97752a1ce5cf16531237fb7141eb0f07464

Tx prefix hash: c9f59e83e20010dba4743e296934e9a5b42368f243e0e07334a56a8fa840288e
Tx public key: 908ba72cacdd69982b4761c9ea9a0fef16760a11783b822e46cee8af0bcc00b5
Timestamp: 1759397693 Timestamp [UCT]: 2025-10-02 09:34:53 Age [y:d:h:m:s]: 00:090:10:20:49
Block: 1381061 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64755 RingCT/type: yes/0
Extra: 01908ba72cacdd69982b4761c9ea9a0fef16760a11783b822e46cee8af0bcc00b5021100000001a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a11cbfc8d56b08a7846706a0eebd66f308f874ea323f8c597a7e1fd3898828dd 0.600000000000 1869174 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": 1381071, "vin": [ { "gen": { "height": 1381061 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a11cbfc8d56b08a7846706a0eebd66f308f874ea323f8c597a7e1fd3898828dd" } } ], "extra": [ 1, 144, 139, 167, 44, 172, 221, 105, 152, 43, 71, 97, 201, 234, 154, 15, 239, 22, 118, 10, 17, 120, 59, 130, 46, 70, 206, 232, 175, 11, 204, 0, 181, 2, 17, 0, 0, 0, 1, 165, 220, 205, 121, 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