Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f1d966c50e3f781e68dbc2dae75abd64308e2f119d9453decebf2cd1a2e35ac

Tx prefix hash: 9ec6b9c27c42658c3bc3dfd34118b79534cf439aa8ad9791869407159cc421c4
Tx public key: 205ee977985f0f87651c2c729971de5afb2f2437d4f5e9093b335b5fd427bb56
Timestamp: 1751325201 Timestamp [UCT]: 2025-06-30 23:13:21 Age [y:d:h:m:s]: 00:131:10:20:07
Block: 1316160 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92114 RingCT/type: yes/0
Extra: 01205ee977985f0f87651c2c729971de5afb2f2437d4f5e9093b335b5fd427bb56021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f433361eaf45e57ccd550cebf26a5cec0d21a64bc1cd3eb39274612ac1f152a7 0.600000000000 1803817 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": 1316170, "vin": [ { "gen": { "height": 1316160 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f433361eaf45e57ccd550cebf26a5cec0d21a64bc1cd3eb39274612ac1f152a7" } } ], "extra": [ 1, 32, 94, 233, 119, 152, 95, 15, 135, 101, 28, 44, 114, 153, 113, 222, 90, 251, 47, 36, 55, 212, 245, 233, 9, 59, 51, 91, 95, 212, 39, 187, 86, 2, 17, 0, 0, 0, 2, 216, 231, 210, 65, 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