Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 223d7e004e2301a8a9df75156d7d29b936691dc1c7952d9eea5e87fc3eef9399

Tx prefix hash: 9d3816330d3121d6054a87125f635e393f4c7b5ee253b3b79e377e65621ba0c4
Tx public key: 5ce2f4e14f69777ebe72772141a356bf6e0f0d7df39647b7b46bf8f54a9c2ac8
Timestamp: 1761001560 Timestamp [UCT]: 2025-10-20 23:06:00 Age [y:d:h:m:s]: 00:074:07:13:31
Block: 1394386 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 53190 RingCT/type: yes/0
Extra: 015ce2f4e14f69777ebe72772141a356bf6e0f0d7df39647b7b46bf8f54a9c2ac80211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a175993899c2eb11d4e7693c138e9e6455060a1719e27298271d03c9f3fdd83 0.600000000000 1882657 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": 1394396, "vin": [ { "gen": { "height": 1394386 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a175993899c2eb11d4e7693c138e9e6455060a1719e27298271d03c9f3fdd83" } } ], "extra": [ 1, 92, 226, 244, 225, 79, 105, 119, 126, 190, 114, 119, 33, 65, 163, 86, 191, 110, 15, 13, 125, 243, 150, 71, 183, 180, 107, 248, 245, 74, 156, 42, 200, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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