Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c5033b3fa4eb2f2622d5dab943c99e45c2674c36f0a1b5fbe7372f2a956b6a9

Tx prefix hash: 56d695b37eab3a2d01c85c41e70fdaa5b8bbb2d9a2cb87d7a8d9bf1de4854a53
Tx public key: fa313c26e3728c2f7e4dc1c4f52b98be8e3425a80b9824e50d9e121d04d43cab
Timestamp: 1750609334 Timestamp [UCT]: 2025-06-22 16:22:14 Age [y:d:h:m:s]: 00:198:19:53:06
Block: 1310556 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140051 RingCT/type: yes/0
Extra: 01fa313c26e3728c2f7e4dc1c4f52b98be8e3425a80b9824e50d9e121d04d43cab0211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ac56186d95afa344e20a13d58a7ac55d19efdc6165756c0a7b7dd61331c75a4f 0.600000000000 1798177 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": 1310566, "vin": [ { "gen": { "height": 1310556 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ac56186d95afa344e20a13d58a7ac55d19efdc6165756c0a7b7dd61331c75a4f" } } ], "extra": [ 1, 250, 49, 60, 38, 227, 114, 140, 47, 126, 77, 193, 196, 245, 43, 152, 190, 142, 52, 37, 168, 11, 152, 36, 229, 13, 158, 18, 29, 4, 212, 60, 171, 2, 17, 0, 0, 0, 2, 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