Pillarproject Pillar Blockchain Explorer API
★ Only Publicly Available OpenAPI DocumentBlockchainBlockchain DataapiKey3 EndpointsREST
For Agents
Query Ethereum transaction history by address, get real-time gas prices across speed tiers, and retrieve gas statistics for wallet and blockchain applications.
Use for: What are the recent transactions for this Ethereum address?, Get the current gas price for a fast transaction, Show me the transaction history for wallet 0x..., What's the recommended gas price right now?
Not supported: Provides read-only blockchain data access for Ethereum and EVM chains. Does not custody assets, sign transactions, or submit transactions to the network. Gas prices are recommendations only and do not guarantee transaction confirmation times.
The Pillar Blockchain Explorer API (BCX API) provides programmatic access to Ethereum and EVM-compatible blockchain data through a REST interface. It exposes transaction history queries, real-time gas price recommendations across multiple speed tiers, and aggregated gas statistics for building wallet applications, transaction monitoring dashboards, and blockchain analytics tools. The API is designed to support the Pillar smart contract wallet ecosystem but is available for general blockchain data access. Jentic publishes enriched documentation for this API, making it discoverable and accessible to AI agents that need reliable blockchain data without operating their own nodes.
Install Jentic One Beta
Connect the Pillar Blockchain Explorer API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Pillar Blockchain Explorer API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Pillar Blockchain Explorer API.
Retrieve transaction history for any Ethereum or EVM address with detailed transaction and receipt data
Get real-time gas price recommendations across safe, standard, fast, and fastest speed tiers
Access aggregated gas statistics including average prices, standard deviation, and block metadata
Query transaction confirmations and status for pending or confirmed transactions
Support for native ETH and ERC-20 token transaction lookups
Obtain current block numbers and block time estimates for transaction timing
Use Cases
Patterns agents use Pillar Blockchain Explorer API for, with concrete tasks.
★ Wallet Transaction History Display
Build a crypto wallet interface that displays complete transaction history for user addresses. The /txHistory endpoint returns detailed transaction data including hash, block number, from/to addresses, value, gas details, confirmation count, and transaction status. Wallet developers can show users their full transaction activity across ETH and ERC-20 tokens with timestamp information, making it easy to track spending, receipts, and pending transactions without running a full Ethereum node.
Query the transaction history endpoint with the user's address and asset type, then format the returned transaction array with hash, timestamp, value, and confirmation status for display in the wallet interface.
Dynamic Gas Price Optimization
Implement intelligent gas price selection for Ethereum transactions by querying real-time gas station data. The /gasStation endpoint provides four gas price tiers (safeLow, standard, fast, fastest) along with current block time and block number, enabling applications to offer users cost-versus-speed trade-offs. DeFi applications, wallets, and automated trading bots can dynamically adjust gas prices based on network conditions, helping users save on fees during low-congestion periods or prioritize speed during time-sensitive operations.
Call the gas station endpoint to retrieve current gas price recommendations, compare the four tiers against the user's urgency requirement, and select the appropriate gas price for transaction submission.
Blockchain Analytics Dashboard
Create blockchain monitoring and analytics dashboards that track network conditions and transaction patterns. The /gasInfo endpoint provides aggregate gas data including average gas price and standard deviation, while transaction history queries enable analysis of address activity patterns. Analytics platforms can monitor gas price trends over time, identify high-activity addresses, track smart contract interactions, and provide insights into network congestion and usage patterns for traders, researchers, and protocol developers.
Aggregate data from gasInfo and txHistory endpoints to calculate network utilization metrics, gas price trends, and transaction volume statistics for visualization in the analytics dashboard.
Transaction Status Monitoring
Build reliable transaction monitoring systems that track transaction confirmation status and automatically notify users or trigger workflows when transactions are confirmed. By querying transaction history with address and transaction hash, applications can monitor the nbConfirmations field and status to determine when transactions have achieved sufficient finality. This is essential for payment processors, DeFi protocols, NFT marketplaces, and any application that needs to wait for on-chain confirmation before proceeding with business logic.
Poll the transaction history endpoint for the specific transaction hash, check the nbConfirmations count against the required threshold (e.g., 12 confirmations), and trigger the confirmation callback when the threshold is met.
Key Endpoints
3 endpoints — the pillar blockchain explorer api (bcx api) provides programmatic access to ethereum and evm-compatible blockchain data through a rest interface.
METHOD
PATH
DESCRIPTION
GET
/txHistory
Retrieve complete transaction history for a specified address and asset, including transaction details, receipts, confirmations, and status
GET
/gasStation
Get current gas price recommendations across four speed tiers (safeLow, standard, fast, fastest) with block time and block number
GET
/gasInfo
Retrieve aggregated gas statistics including average gas price, standard deviation, and the latest block number
GET
/txHistory
Retrieve complete transaction history for a specified address and asset, including transaction details, receipts, confirmations, and status
GET
/gasStation
Get current gas price recommendations across four speed tiers (safeLow, standard, fast, fastest) with block time and block number
GET
/gasInfo
Retrieve aggregated gas statistics including average gas price, standard deviation, and the latest block number
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
API key stored in Jentic vault, passed as authentication header on each request without exposing credentials in agent context
Intent-based discovery
Natural language search for 'ethereum transaction history' or 'gas price api' surfaces Pillar endpoints with parameter schemas and example responses
Time to first call
Agents load endpoint schemas on-demand and execute within 2-3 seconds of user request, no SDK installation or node infrastructure required
Related APIs
Alternatives and complements available in the Jentic catalogue.
Complementary
Alternative
Complementary
FAQs
Specific to using Pillar Blockchain Explorer API through Jentic.
What is the Pillar Blockchain Explorer API?
The Pillar Blockchain Explorer API is a REST interface for accessing Ethereum and EVM-compatible blockchain data, including transaction history, gas prices, and network statistics. It provides three main endpoints for transaction queries, real-time gas recommendations, and aggregated gas data.
How do I authenticate with the Pillar API?
The Pillar Blockchain Explorer API uses API key authentication. You configure the API URL and authentication when initializing the SDK or making direct HTTP requests. Contact Pillar Project or check their developer documentation for API key provisioning.
What blockchain networks does the Pillar API support?
The Pillar Blockchain Explorer API supports Ethereum mainnet and EVM-compatible chains. It can query transaction history for native ETH and ERC-20 tokens, making it suitable for multi-chain wallet applications built on Ethereum-compatible networks.
What gas price tiers are available from the gas station endpoint?
The gas station endpoint provides four gas price tiers: safeLow (most economical), standard (average speed), fast (quicker confirmation), and fastest (priority confirmation). Each tier is returned in Gwei along with the current block time and block number.
Can I use this API to submit transactions to the blockchain?
The Pillar Blockchain Explorer API is designed for reading blockchain data, not submitting transactions. It provides transaction history queries and gas price recommendations, but transaction signing and submission would typically be handled by wallet SDKs or web3 libraries that interact directly with Ethereum nodes.
How is this API different from running my own Ethereum node?
The Pillar Blockchain Explorer API provides a hosted REST interface to blockchain data, eliminating the need to run, maintain, and sync your own Ethereum node. It offers formatted, easy-to-consume endpoints for common wallet and application needs like transaction history and gas prices, whereas a full node requires more technical infrastructure and provides raw blockchain access.
GET STARTED