Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aec94594a37b7df5c2a383b10b12b195a7d3834b09d237b5583e370eb0811d34

Tx prefix hash: c60cbe20f0723c4abbf8c52ec03579690b4571c650e5d0a5b4062905595d61f0
Tx public key: e0f7db14fb30c540f6d8e502ca6b37b561247f595875ad7ff5ba45de43ee917c
Timestamp: 1751622721 Timestamp [UCT]: 2025-07-04 09:52:01 Age [y:d:h:m:s]: 00:185:16:35:07
Block: 1318545 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 131047 RingCT/type: yes/0
Extra: 01e0f7db14fb30c540f6d8e502ca6b37b561247f595875ad7ff5ba45de43ee917c021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: deb104dba98a91149df5d5e720190e8041baf62dd698f81a7b1045ddcae230c7 0.600000000000 1806230 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": 1318555, "vin": [ { "gen": { "height": 1318545 } } ], "vout": [ { "amount": 600000000, "target": { "key": "deb104dba98a91149df5d5e720190e8041baf62dd698f81a7b1045ddcae230c7" } } ], "extra": [ 1, 224, 247, 219, 20, 251, 48, 197, 64, 246, 216, 229, 2, 202, 107, 55, 181, 97, 36, 127, 89, 88, 117, 173, 127, 245, 186, 69, 222, 67, 238, 145, 124, 2, 17, 0, 0, 0, 1, 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