Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec96d8c7622069225c52bf019c6d55d775bd2cb02c883c07d52f4a93466dca21

Tx prefix hash: ae026e3b1fe62e89df225092d0febfdf317aa941626185b1d0dd869b10bedd5c
Tx public key: 0888505425a8dd339d1519fd30c00dbbdc4713ae8c977b407e768dff95ecbdf6
Timestamp: 1747246224 Timestamp [UCT]: 2025-05-14 18:10:24 Age [y:d:h:m:s]: 00:235:07:24:56
Block: 1282919 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165939 RingCT/type: yes/0
Extra: 010888505425a8dd339d1519fd30c00dbbdc4713ae8c977b407e768dff95ecbdf6021100000002dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 84eab9b3cf3c8e20ff0c31fe02da93378c8550adb2508f22be20f3dcf31aa037 0.600000000000 1770334 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": 1282929, "vin": [ { "gen": { "height": 1282919 } } ], "vout": [ { "amount": 600000000, "target": { "key": "84eab9b3cf3c8e20ff0c31fe02da93378c8550adb2508f22be20f3dcf31aa037" } } ], "extra": [ 1, 8, 136, 80, 84, 37, 168, 221, 51, 157, 21, 25, 253, 48, 192, 13, 187, 220, 71, 19, 174, 140, 151, 123, 64, 126, 118, 141, 255, 149, 236, 189, 246, 2, 17, 0, 0, 0, 2, 223, 195, 186, 73, 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