Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9205c745c24e598499e71a05e956068f00f4aacebf133abc8a5d508e34b08e42

Tx prefix hash: b1df44840f18f4bc110ffb0b80fe9b81ba925445808f5ecd273163d15478282b
Tx public key: dae8fe995e2991c71c1ac2af854cfbbbd22c3324ccbbb0b0dd6a239cb552beff
Timestamp: 1765156262 Timestamp [UCT]: 2025-12-08 01:11:02 Age [y:d:h:m:s]: 00:052:11:58:38
Block: 1428788 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 37408 RingCT/type: yes/0
Extra: 01dae8fe995e2991c71c1ac2af854cfbbbd22c3324ccbbb0b0dd6a239cb552beff021100000002d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 53f6a9f9b5a1a7dfd09cccd531c8a38d638ea21558ceb0cc5410c3224c89f295 0.600000000000 1917511 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": 1428798, "vin": [ { "gen": { "height": 1428788 } } ], "vout": [ { "amount": 600000000, "target": { "key": "53f6a9f9b5a1a7dfd09cccd531c8a38d638ea21558ceb0cc5410c3224c89f295" } } ], "extra": [ 1, 218, 232, 254, 153, 94, 41, 145, 199, 28, 26, 194, 175, 133, 76, 251, 187, 210, 44, 51, 36, 204, 187, 176, 176, 221, 106, 35, 156, 181, 82, 190, 255, 2, 17, 0, 0, 0, 2, 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