Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5488861f32f85dc6941af5cfb5b17128d5eb5bfe92102394d8775f330efef03

Tx prefix hash: dd6c56d61f0cff45d62a32a159bf61fc0e4fcb705a10ade7ba2a77058e19ee76
Tx public key: 9bec8f816c0e81ffb3821db8c4eef6f5a0d2ee7f2b86dbc4aa3b4a2a89dfb3c0
Timestamp: 1752767069 Timestamp [UCT]: 2025-07-17 15:44:29 Age [y:d:h:m:s]: 00:034:03:26:49
Block: 1327509 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 23264 RingCT/type: yes/0
Extra: 019bec8f816c0e81ffb3821db8c4eef6f5a0d2ee7f2b86dbc4aa3b4a2a89dfb3c002110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7696b58c87c42f520afc9c52a8dae8247a4255c0e17cb445cad55611c29a9ee6 0.600000000000 1815264 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": 1327519, "vin": [ { "gen": { "height": 1327509 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7696b58c87c42f520afc9c52a8dae8247a4255c0e17cb445cad55611c29a9ee6" } } ], "extra": [ 1, 155, 236, 143, 129, 108, 14, 129, 255, 179, 130, 29, 184, 196, 238, 246, 245, 160, 210, 238, 127, 43, 134, 219, 196, 170, 59, 74, 42, 137, 223, 179, 192, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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