Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da802e8a4f9cf478ac56d6093c5f4659213f429e8d7fbeef84e6eebf8658a9ec

Tx prefix hash: 497dc087b3068ee37cd9f787158df9517e954ae26c7769372bcf15f05a802c11
Tx public key: 9495a6306e790c805a1327e0a0ae76f707a6f47272c65962c33a4a118e1d93f7
Timestamp: 1751824087 Timestamp [UCT]: 2025-07-06 17:48:07 Age [y:d:h:m:s]: 00:130:19:52:44
Block: 1320066 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 91913 RingCT/type: yes/0
Extra: 019495a6306e790c805a1327e0a0ae76f707a6f47272c65962c33a4a118e1d93f7021100000004d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8916eab6fbff4e83870aaaaa925c4a632bdb2e08dcdbcb32a95d1b5d86890bba 0.600000000000 1807761 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": 1320076, "vin": [ { "gen": { "height": 1320066 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8916eab6fbff4e83870aaaaa925c4a632bdb2e08dcdbcb32a95d1b5d86890bba" } } ], "extra": [ 1, 148, 149, 166, 48, 110, 121, 12, 128, 90, 19, 39, 224, 160, 174, 118, 247, 7, 166, 244, 114, 114, 198, 89, 98, 195, 58, 74, 17, 142, 29, 147, 247, 2, 17, 0, 0, 0, 4, 216, 231, 210, 65, 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