Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61bd68625c52c3aa398e2329c5504b7bd5739a53084a8624b7c6c3754aa7a988

Tx prefix hash: e139159d61f593be8a6c541da3335f7d6c43f08318078be2d6f3ebc9b8aac6f5
Tx public key: 69e35995d352cc0f730a3bdbbdc728eedbe5b82445de5a214cd6f2827573390e
Timestamp: 1765097606 Timestamp [UCT]: 2025-12-07 08:53:26 Age [y:d:h:m:s]: 00:000:18:05:56
Block: 1428304 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 542 RingCT/type: yes/0
Extra: 0169e35995d352cc0f730a3bdbbdc728eedbe5b82445de5a214cd6f2827573390e0211000000017b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6b4f99bab35b45dad151ea63edb954984549581f47d0fa33232a4b8ea41422ae 0.600000000000 1917021 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": 1428314, "vin": [ { "gen": { "height": 1428304 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6b4f99bab35b45dad151ea63edb954984549581f47d0fa33232a4b8ea41422ae" } } ], "extra": [ 1, 105, 227, 89, 149, 211, 82, 204, 15, 115, 10, 59, 219, 189, 199, 40, 238, 219, 229, 184, 36, 69, 222, 90, 33, 76, 214, 242, 130, 117, 115, 57, 14, 2, 17, 0, 0, 0, 1, 123, 30, 81, 172, 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