Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4cd2ebe82b3e6d8c4917ead365828f361763f570c943c6f99c6234f4d5accb73

Tx prefix hash: 9fe73f9e4c83cda1bc31843437ec3dc6d10f860ad714d0c17a2548c50d9cc5e3
Tx public key: ddc28157713b5613d3548afe65ab29ccd66635c2f4df0a2516e145e76884a916
Timestamp: 1733987469 Timestamp [UCT]: 2024-12-12 07:11:09 Age [y:d:h:m:s]: 00:109:10:24:18
Block: 1173429 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77983 RingCT/type: yes/0
Extra: 01ddc28157713b5613d3548afe65ab29ccd66635c2f4df0a2516e145e76884a9160211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a62b56c727f8416545713c484ea947704d5e572ef76166f4a14b6282ab12575d 0.600000000000 1659450 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": 1173439, "vin": [ { "gen": { "height": 1173429 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a62b56c727f8416545713c484ea947704d5e572ef76166f4a14b6282ab12575d" } } ], "extra": [ 1, 221, 194, 129, 87, 113, 59, 86, 19, 211, 84, 138, 254, 101, 171, 41, 204, 214, 102, 53, 194, 244, 223, 10, 37, 22, 225, 69, 231, 104, 132, 169, 22, 2, 17, 0, 0, 0, 3, 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