Fetch a decoded transaction
Raw transactions give you calldata and logs, not meaning. The decoded endpoint resolves the called method, its arguments and emitted transfers against known ABIs. You get structured data without maintaining an ABI registry or running a node.
- An API key (sk_live_...) with C1 read access.
- A transaction hash on eth or tron.
1Request the decoded transaction
GET the decoded path with the transaction hash. Recent transactions are C1; older ones served from archive depth are C2.
curl https://api.1st-node.com/v1/data/eth/tx/0x8f2a...c91b/decoded \ -H "Authorization: Bearer sk_live_..."
2Inspect the decoded method and args
The response names the method, lists typed arguments and expands token transfers with symbols and amounts, so you skip ABI decoding entirely.
> {
> "hash": "0x8f2a...c91b",
> "method": "transfer(address,uint256)",
> "args": { "to": "0x53d2...9a1f", "value": "5000000" },
> "transfers": [
> { "token": "USDC", "from": "0x1f3c...", "to": "0x53d2...9a1f", "amount": "5000000" }
> ],
> "status": "success"
> }3Fall back to raw calldata if needed
For contracts without a known ABI, the raw input is still returned. You can also fetch the raw form over standard JSON-RPC if you prefer to decode client-side.
curl https://api.1st-node.com/v1/rpc/eth \
-H "Authorization: Bearer sk_live_..." \
-d '{"method":"eth_getTransactionByHash","params":["0x8f2a...c91b"]}'Sıkça sorulanlar
What is a decoded transaction?
It is a raw transaction resolved against contract ABIs so the called method, its typed arguments and token transfers are readable instead of hex calldata.
Does old transaction history cost more?
Recent reads are C1. Archive-depth history is served from our own archive nodes at C2, so you still pay per call rather than running an archive node yourself.
Okumaya devam et
Bakiye yükle, anahtarını al, yayına çık.
Self servis. Kripto ya da kartla öde. Krediyle ölçümlenir — ağır ilkel yapılar daha pahalı, basitler ucuz.
API anahtarı al