Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa6d9600232700d0643bde4e8a19171f01ddb625f84060da9c62b18a31dc8ff2

Tx prefix hash: 02d8537e3fb67aabbbe23717e47169d802214a4deb7542e3df3c1f35f5d9a737
Tx public key: 62b0353992af58844e5ace371b4f27a0f5b30361438f207fd5a30e7de06de990
Timestamp: 1758797494 Timestamp [UCT]: 2025-09-25 10:51:34 Age [y:d:h:m:s]: 00:092:17:51:02
Block: 1376095 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66407 RingCT/type: yes/0
Extra: 0162b0353992af58844e5ace371b4f27a0f5b30361438f207fd5a30e7de06de990021100000003b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d76ef71b5e8383b5c18e07b5b8ba22fa5ab914da9eb031ccdbc82ee6c7c0b5f2 0.600000000000 1864186 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": 1376105, "vin": [ { "gen": { "height": 1376095 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d76ef71b5e8383b5c18e07b5b8ba22fa5ab914da9eb031ccdbc82ee6c7c0b5f2" } } ], "extra": [ 1, 98, 176, 53, 57, 146, 175, 88, 132, 78, 90, 206, 55, 27, 79, 39, 160, 245, 179, 3, 97, 67, 143, 32, 127, 213, 163, 14, 125, 224, 109, 233, 144, 2, 17, 0, 0, 0, 3, 178, 247, 132, 196, 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