React Frontends
Last updated
Last updated
Transactions that fail in the client/frontend cannot be found in a block explorer as the transaction never makes it into the mempool and subsequently on chain. For that reason, the Blocktorch team developed , an SDK that can easily be added to dApp frontends utilizing .
With Dragon you can track failing and successful web3 client transactions for as well as analytics.
json RPC responses, especially error messages, in the UI are cryptic
to understand whether errors impacting users are a bug in the frontend or the smart contract
to get better analytics about the wallets interacting with your dApp
to understand if wallets are interacting with your smart contracts through your dApp frontend or through their own scripts, which can especially be helpful for security
or if you prefer yarn
In the constructor you can also specify additional options:
contractName
(string) - default identifier for what the transactions are interacting with. Default is "unknown"
chainId
(number) - chain ID of the application
http
(object):
maxRetries
(number) - number of times failed SDK requests are retried
delay
(number) - number of times failed SDK requests are retried
exponentialBackoff
(boolean) - Whether to allow exponential backoff or not
Initialize the tracking of a single transaction
You can override options per transaction.
contract
(string) - identifier for what the transaction is interacting with
chainId
(number) - id of the blockchain
Track the transaction as a success. Should be done after the transaction is accepted on chain.
Track the transaction as an error
If you are using ethers@5 or any other compatible libraries you can use a helper function to wrap your whole transaction and it will detect success or failure itself. It will wait until the transaction receipt is received to mark it as a success.
You can also specify the following options:
contract
(string) - identifier for what the transaction is interacting with
chainId
(number) - id of the blockchain
You can get your project ID and api key from the on the "Settings" page
All dragon data can be queried for as well as when logs. For successful transactions we automatically contextualize your transaction logs with dragon data to show the full