Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d143924695130a119570df56ee8a3f6625bbce609205a93f0edbecaf8ac2bbe

Tx prefix hash: f2035f1f381eced1d951b130c362b856dfb9edda61394a7fc16fa451d3b21653
Tx public key: d3e3711768cf565f1aaddc43d26d004e2db810a40ef8c708a0ce86dc7a10629c
Timestamp: 1726712326 Timestamp [UCT]: 2024-09-19 02:18:46 Age [y:d:h:m:s]: 00:202:20:21:18
Block: 1113205 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 144796 RingCT/type: yes/0
Extra: 01d3e3711768cf565f1aaddc43d26d004e2db810a40ef8c708a0ce86dc7a10629c02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6ee511ee323e0e1a9d7f2e869fcf05a7e0bda0b8046fd89272088c0d87cee94d 0.600000000000 1592794 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": 1113215, "vin": [ { "gen": { "height": 1113205 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ee511ee323e0e1a9d7f2e869fcf05a7e0bda0b8046fd89272088c0d87cee94d" } } ], "extra": [ 1, 211, 227, 113, 23, 104, 207, 86, 95, 26, 173, 220, 67, 210, 109, 0, 78, 45, 184, 16, 164, 14, 248, 199, 8, 160, 206, 134, 220, 122, 16, 98, 156, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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