Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d7a53b2bd1865a4da24b9197d3ad2d4210657555f794ca931b3a7fd79bab4fce

Tx prefix hash: d9a1af56e3534cfd6f03638b30b41bc7eeebd66b5db46f1b666280d2667d31b4
Tx public key: 237f7df8b9e57b0b9bed1f35387672fadd98ca800126caab9f17f9cc9cd7a8b0
Timestamp: 1754975285 Timestamp [UCT]: 2025-08-12 05:08:05 Age [y:d:h:m:s]: 00:144:08:47:51
Block: 1345251 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102544 RingCT/type: yes/0
Extra: 01237f7df8b9e57b0b9bed1f35387672fadd98ca800126caab9f17f9cc9cd7a8b002110000001aad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ada5fc5dd55de2b2c0544318e553cf545f7fbfd26364b13fb46c769957d89717 0.600000000000 1833142 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": 1345261, "vin": [ { "gen": { "height": 1345251 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ada5fc5dd55de2b2c0544318e553cf545f7fbfd26364b13fb46c769957d89717" } } ], "extra": [ 1, 35, 127, 125, 248, 185, 229, 123, 11, 155, 237, 31, 53, 56, 118, 114, 250, 221, 152, 202, 128, 1, 38, 202, 171, 159, 23, 249, 204, 156, 215, 168, 176, 2, 17, 0, 0, 0, 26, 173, 121, 72, 208, 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