Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: accedbd8d888c21eb8c19285be96613c55baf441fb0299da522c4efd83fe7b17

Tx prefix hash: df313aec6a7830191fc8374f9e293f440287a9b7d626c0caa0a9d41aa90b0c6c
Tx public key: 8643e9bbfc82ca29f0175f07771f0a0111b11c7cfa84c51fd534ef66b4117784
Timestamp: 1712259524 Timestamp [UCT]: 2024-04-04 19:38:44 Age [y:d:h:m:s]: 00:220:10:23:20
Block: 993371 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157810 RingCT/type: yes/0
Extra: 018643e9bbfc82ca29f0175f07771f0a0111b11c7cfa84c51fd534ef66b411778402110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d1a566a2ab0be1e0fa487be9c2fe77cbc77d4c05c34280cffeb6a464b128df08 0.600000000000 1453757 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": 993381, "vin": [ { "gen": { "height": 993371 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d1a566a2ab0be1e0fa487be9c2fe77cbc77d4c05c34280cffeb6a464b128df08" } } ], "extra": [ 1, 134, 67, 233, 187, 252, 130, 202, 41, 240, 23, 95, 7, 119, 31, 10, 1, 17, 177, 28, 124, 250, 132, 197, 31, 213, 52, 239, 102, 180, 17, 119, 132, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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