Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9cd093a4c8c23514bc5995f5a7e692d7bb8841ce894f87bd8bdf6a7cdf0e8a3c

Tx prefix hash: dd00e0452c95da07882cbcd0ad60f2e62f8cd82617a2b4a76703cdd167543cca
Tx public key: 82164f35c001bd31e227a0f8a48c6974571afb4730d107b9312137bea3b6efd1
Timestamp: 1750460408 Timestamp [UCT]: 2025-06-20 23:00:08 Age [y:d:h:m:s]: 00:153:09:47:19
Block: 1309347 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107481 RingCT/type: yes/0
Extra: 0182164f35c001bd31e227a0f8a48c6974571afb4730d107b9312137bea3b6efd102110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0bd4263947ca5c1456c165a92e6b31d2cc10b21b0d340968b7e00b0e49d236d7 0.600000000000 1796962 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": 1309357, "vin": [ { "gen": { "height": 1309347 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0bd4263947ca5c1456c165a92e6b31d2cc10b21b0d340968b7e00b0e49d236d7" } } ], "extra": [ 1, 130, 22, 79, 53, 192, 1, 189, 49, 226, 39, 160, 248, 164, 140, 105, 116, 87, 26, 251, 71, 48, 209, 7, 185, 49, 33, 55, 190, 163, 182, 239, 209, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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