Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9856d3a43fd3f8eb767ee3f39354d72b90963c5d40a30c064512a7e955d0a958

Tx prefix hash: a4f7b6413dbaba729796f313958fc13058e1343c4a6c6570cff6a0d8bac22fb6
Tx public key: 211ba93d98ed1b28196a7273baae2bceb3c7ff9cfc639d9a604f9a84dd96a673
Timestamp: 1751611419 Timestamp [UCT]: 2025-07-04 06:43:39 Age [y:d:h:m:s]: 00:139:01:39:24
Block: 1318449 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97665 RingCT/type: yes/0
Extra: 01211ba93d98ed1b28196a7273baae2bceb3c7ff9cfc639d9a604f9a84dd96a673021100000028bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a476e2b207739427fa53f80ca7f18a4eec84a0a67a5284360245700013e52d28 0.600000000000 1806130 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": 1318459, "vin": [ { "gen": { "height": 1318449 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a476e2b207739427fa53f80ca7f18a4eec84a0a67a5284360245700013e52d28" } } ], "extra": [ 1, 33, 27, 169, 61, 152, 237, 27, 40, 25, 106, 114, 115, 186, 174, 43, 206, 179, 199, 255, 156, 252, 99, 157, 154, 96, 79, 154, 132, 221, 150, 166, 115, 2, 17, 0, 0, 0, 40, 191, 81, 178, 162, 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