Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 111dce9256a68d8d1278f9443eeae50149992668256e684b5e43b5d3fa666def

Tx prefix hash: dc5d5cf7db3ec4903f594fb57f941cbc57d38a7bb8d51e1f0d9236cb64c7f8d6
Tx public key: 0be59acb726849b65715f83cb24285a9d40e0f7529e21d9322b32ea7ce1bd2dd
Timestamp: 1735070300 Timestamp [UCT]: 2024-12-24 19:58:20 Age [y:d:h:m:s]: 00:087:23:10:10
Block: 1182390 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 62642 RingCT/type: yes/0
Extra: 010be59acb726849b65715f83cb24285a9d40e0f7529e21d9322b32ea7ce1bd2dd0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6b8bc2fd549936dc0c982292eb62a50ab5d0c9af7d06c75929cb7ea1aa4c1a6f 0.600000000000 1668823 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": 1182400, "vin": [ { "gen": { "height": 1182390 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6b8bc2fd549936dc0c982292eb62a50ab5d0c9af7d06c75929cb7ea1aa4c1a6f" } } ], "extra": [ 1, 11, 229, 154, 203, 114, 104, 73, 182, 87, 21, 248, 60, 178, 66, 133, 169, 212, 14, 15, 117, 41, 226, 29, 147, 34, 179, 46, 167, 206, 27, 210, 221, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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