Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2de0fcae4ad07b88b634ada005fd9c66a302e2ef523e70c7f0cf69bc85dca70

Tx prefix hash: a83c2e9282944955310adfee1d04e1071bddde43c9d13b9d9cdc4bcb3a84264f
Tx public key: d63313a22b4201fc6fdfa0a00892d1e55e0a70f7783d8cb8db3650700f98053d
Timestamp: 1759723496 Timestamp [UCT]: 2025-10-06 04:04:56 Age [y:d:h:m:s]: 00:086:17:43:32
Block: 1383762 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 62110 RingCT/type: yes/0
Extra: 01d63313a22b4201fc6fdfa0a00892d1e55e0a70f7783d8cb8db3650700f98053d021100000004a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c3d82389137fb31e8f7f361293af20d69577b8e9f6d1dfa66794f6bab3416fa8 0.600000000000 1871909 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": 1383772, "vin": [ { "gen": { "height": 1383762 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c3d82389137fb31e8f7f361293af20d69577b8e9f6d1dfa66794f6bab3416fa8" } } ], "extra": [ 1, 214, 51, 19, 162, 43, 66, 1, 252, 111, 223, 160, 160, 8, 146, 209, 229, 94, 10, 112, 247, 120, 61, 140, 184, 219, 54, 80, 112, 15, 152, 5, 61, 2, 17, 0, 0, 0, 4, 165, 220, 205, 121, 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