Transaction Status Verification

Use this skill to fetch on-chain data for a given transaction hash. This is critical for verifying the outcome of send or trade operations.

Hard Rules (CRITICAL)

•Verification: After performing a send or trade, you MUST use this skill if the user asks "did it go through?" or "show me the link".
•Chain Specificity: If the transaction was on a specific chain (e.g., Monad), you MUST verify the status on that same chain using the --chain flag.

Usage

Check Status

bash

npx fibx tx-status <hash> [--chain <chain>]

•<hash>: The transaction hash (starting with 0x).
•--chain <chain>: Optional. The network the transaction was sent on (base, citrea, hyperevm, monad). Defaults to base.

Examples

Scenario 1: Check a Base transaction (Default)

Input: "Check status of 0x123...456"

bash

npx fibx tx-status 0x123...456

Scenario 2: Check a Monad transaction

Input: "Verify tx 0xabc...def on Monad"

bash

npx fibx tx-status 0xabc...def --chain monad

JSON Output (for programmatic parsing)

Use --json to get a machine-readable response:

bash

npx fibx tx-status 0x123...456 --json

Output Schema:

json

{
	"status": "success", // "success" or "reverted"
	"blockNumber": "12345", // Block number where included
	"gasUsed": "21000", // Gas used
	"explorerLink": "https://..." // URL to block explorer
}

Error Handling

•Transaction not found: If the TX is not found, ensure you are querying the correct chain.
•Pending: The CLI may hang or return "pending" if the tx is still in the mempool.