Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1762120334a7c10ae017b759523ea6fe38a4524bddc338cb22dace06d4fdb238

Tx prefix hash: 481727f8b7c12da24067445464b79339b97611979a006e072d832aa04a2b3a96
Tx public key: bfe766d1a2505b7dcbec69ec7fba74af8562b54e6f90a902591c5db5dac0a1f9
Timestamp: 1729116871 Timestamp [UCT]: 2024-10-16 22:14:31 Age [y:d:h:m:s]: 00:148:17:22:46
Block: 1133142 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106075 RingCT/type: yes/0
Extra: 01bfe766d1a2505b7dcbec69ec7fba74af8562b54e6f90a902591c5db5dac0a1f90211000000063cd0fc06000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c6b8254b39eb592b6751926f304bd129fdefdd9aa3013d654aed0fc3d5f13053 0.600000000000 1616211 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": 1133152, "vin": [ { "gen": { "height": 1133142 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c6b8254b39eb592b6751926f304bd129fdefdd9aa3013d654aed0fc3d5f13053" } } ], "extra": [ 1, 191, 231, 102, 209, 162, 80, 91, 125, 203, 236, 105, 236, 127, 186, 116, 175, 133, 98, 181, 78, 111, 144, 169, 2, 89, 28, 93, 181, 218, 192, 161, 249, 2, 17, 0, 0, 0, 6, 60, 208, 252, 6, 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