Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dfa357fc0ed81a81d390ad17f3f9eb161ff6f81f106dc41f55a761133146ecab

Tx prefix hash: 6730701204c929133ef6980be4fcece8f759e2374f9c2b94a461d1885ba010bc
Tx public key: d1ff7f351f242658a2f7e2b37ddbb84b5734f37b6dfd65de0811d0a983136a51
Timestamp: 1723293424 Timestamp [UCT]: 2024-08-10 12:37:04 Age [y:d:h:m:s]: 00:225:14:08:38
Block: 1084861 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161097 RingCT/type: yes/0
Extra: 01d1ff7f351f242658a2f7e2b37ddbb84b5734f37b6dfd65de0811d0a983136a51021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 607acfa045da06545ab971e0a9e6e709d89a9c01043aec8cee568a9ab868a50b 0.600000000000 1559292 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": 1084871, "vin": [ { "gen": { "height": 1084861 } } ], "vout": [ { "amount": 600000000, "target": { "key": "607acfa045da06545ab971e0a9e6e709d89a9c01043aec8cee568a9ab868a50b" } } ], "extra": [ 1, 209, 255, 127, 53, 31, 36, 38, 88, 162, 247, 226, 179, 125, 219, 184, 75, 87, 52, 243, 123, 109, 253, 101, 222, 8, 17, 208, 169, 131, 19, 106, 81, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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