Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c932d2fd560fe55f5a3f60df910684ca7e563858b054e2125323f9675138a15d

Tx prefix hash: 06940f8248507409781f0e401341ec9d8fee5a53f5948b38162344fc4a28021f
Tx public key: a9a0f71123a238981f8b01514f929236eb5b28249ef46a1aeb3c41ffd45bd754
Timestamp: 1751728604 Timestamp [UCT]: 2025-07-05 15:16:44 Age [y:d:h:m:s]: 00:127:06:48:31
Block: 1319335 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 89322 RingCT/type: yes/0
Extra: 01a9a0f71123a238981f8b01514f929236eb5b28249ef46a1aeb3c41ffd45bd75402110000000343846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ed0851c1e0f49bfb60cc814e6126f7b562134e1ec720951e1f517b462f8a535 0.600000000000 1807026 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": 1319345, "vin": [ { "gen": { "height": 1319335 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ed0851c1e0f49bfb60cc814e6126f7b562134e1ec720951e1f517b462f8a535" } } ], "extra": [ 1, 169, 160, 247, 17, 35, 162, 56, 152, 31, 139, 1, 81, 79, 146, 146, 54, 235, 91, 40, 36, 158, 244, 106, 26, 235, 60, 65, 255, 212, 91, 215, 84, 2, 17, 0, 0, 0, 3, 67, 132, 109, 102, 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