Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9df4814d712def4a139e6bfe97de6dbfa43e5c5d988ae074976aeac11333a47f

Tx prefix hash: 60f2393461dea623bac4b4b15137b35cf7d2c5dea525e56677c87f074c3b7f38
Tx public key: cfe4dccec1c2a2106d231190264b6ab85ac4c8f00a37669bdf51c341b3bf41e6
Timestamp: 1761988043 Timestamp [UCT]: 2025-11-01 09:07:23 Age [y:d:h:m:s]: 00:005:13:08:11
Block: 1402564 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3941 RingCT/type: yes/0
Extra: 01cfe4dccec1c2a2106d231190264b6ab85ac4c8f00a37669bdf51c341b3bf41e6021100000002df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1bbd36bc86e8bd5ad6398214dbd09abbf1948c39619b7954361f5b275b745741 0.600000000000 1890883 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": 1402574, "vin": [ { "gen": { "height": 1402564 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1bbd36bc86e8bd5ad6398214dbd09abbf1948c39619b7954361f5b275b745741" } } ], "extra": [ 1, 207, 228, 220, 206, 193, 194, 162, 16, 109, 35, 17, 144, 38, 75, 106, 184, 90, 196, 200, 240, 10, 55, 102, 155, 223, 81, 195, 65, 179, 191, 65, 230, 2, 17, 0, 0, 0, 2, 223, 90, 36, 122, 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