Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c073ad8df7cd977f392c4232fb0a556cd53599e09badb2bf312b580fb91d318f

Tx prefix hash: 880d5a4be6949da7c613b63bbbd4e9b9ad6bffc48807522e1c2c3041feecbaf6
Tx public key: 5ba73b57c5e773b031c7539d7ef75272a3c3eca590a9c48a50777f7611a2d86e
Timestamp: 1763281499 Timestamp [UCT]: 2025-11-16 08:24:59 Age [y:d:h:m:s]: 00:012:02:43:11
Block: 1413253 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8671 RingCT/type: yes/0
Extra: 015ba73b57c5e773b031c7539d7ef75272a3c3eca590a9c48a50777f7611a2d86e021100000003d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a8489da4c17290d24c9ea1bad11a9854bdd8b12ae16e2fa651696bc5b4fad715 0.600000000000 1901730 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": 1413263, "vin": [ { "gen": { "height": 1413253 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a8489da4c17290d24c9ea1bad11a9854bdd8b12ae16e2fa651696bc5b4fad715" } } ], "extra": [ 1, 91, 167, 59, 87, 197, 231, 115, 176, 49, 199, 83, 157, 126, 247, 82, 114, 163, 195, 236, 165, 144, 169, 196, 138, 80, 119, 127, 118, 17, 162, 216, 110, 2, 17, 0, 0, 0, 3, 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