Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 418e88fd8f2cf35f7c239f3a7b22772b9ad422561f459639eaaaf7515e014e33

Tx prefix hash: f9df0d3d8747f872eeacb66afe7e9cd8c0f1e19ea690764a45442fd997cb2763
Tx public key: 787a2c279b1882e6b8751fdd2bb5411d5dda8281a56addd476c3040994e58b7d
Timestamp: 1762789763 Timestamp [UCT]: 2025-11-10 15:49:23 Age [y:d:h:m:s]: 00:043:07:00:09
Block: 1409185 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 30979 RingCT/type: yes/0
Extra: 01787a2c279b1882e6b8751fdd2bb5411d5dda8281a56addd476c3040994e58b7d02110000000170609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 340b6369f2bdba3f4cef4c0f340e1780371bbf46f3381a5d3d942b6ec4b7e27b 0.600000000000 1897618 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": 1409195, "vin": [ { "gen": { "height": 1409185 } } ], "vout": [ { "amount": 600000000, "target": { "key": "340b6369f2bdba3f4cef4c0f340e1780371bbf46f3381a5d3d942b6ec4b7e27b" } } ], "extra": [ 1, 120, 122, 44, 39, 155, 24, 130, 230, 184, 117, 31, 221, 43, 181, 65, 29, 93, 218, 130, 129, 165, 106, 221, 212, 118, 195, 4, 9, 148, 229, 139, 125, 2, 17, 0, 0, 0, 1, 112, 96, 157, 3, 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