GET
/
api
/
v1
/
developer
/
{chain}
/
raw
/
transactions
/
{transaction_hash}
Get Transaction
curl --request GET \
  --url https://api.allium.so/api/v1/developer/{chain}/raw/transactions/{transaction_hash} \
  --header 'X-API-KEY: <api-key>'
{
  "hash": "<string>",
  "block_timestamp": "2023-11-07T05:31:56Z",
  "nonce": 0,
  "transaction_index": 0,
  "from_address": "<string>",
  "to_address": "<string>",
  "value": "<string>",
  "gas": 0,
  "gas_price": 0,
  "input": "<string>",
  "receipt_cumulative_gas_used": 0,
  "receipt_gas_used": 0,
  "receipt_contract_address": "<string>",
  "receipt_root": "<string>",
  "receipt_status": 0,
  "block_number": 0,
  "block_hash": "<string>",
  "max_fee_per_gas": 0,
  "max_priority_fee_per_gas": 0,
  "transaction_type": 0,
  "receipt_effective_gas_price": 0,
  "function_signature": "<string>",
  "action": "<string>"
}

Transactions are cryptographically signed instructions from accounts.

An account will initiate a transaction to update the state of the Ethereum network. Transactions always originate from an externally owned account (a smart contract can not initiate a transaction). Transactions, which change the state of the EVM, need to be broadcast to the whole network. Any node can broadcast a request for a transaction to be executed on the EVM; after this happens, a validator will execute the transaction and propagate the resulting state change to the rest of the network.

​
Action labels

When using the API, transactions are enriched with action labels that convey the primary intention of the transaction from the perspective of the wallet that created the transaction. Action labeling coverage is not guaranteed to be exhaustive, but will be improved over time.

​
Supported labels

CategoryNameStatusNameDescription
DEXdex_swap

✅

dex_swap
DEXdex_add_liquidity

✅

dex_add_liquidity
DEXdex_remove_liquidty

✅

dex_remove_liquidity
DEXdex_deploy_liquidity_pool

✅

dex_deploy_liquidity_pool
NFTnft_buy

✅

nft_buy
NFTnft_sell

✅

nft_
NFTnft_mint

✅

Authorizations

​
X-API-KEY
string
header
required

Path Parameters

​
chain
enum<string>
required
Available options:
abstract,
aleph_zero,
alienx,
apechain,
aptos,
arbitrum,
arbitrum_nova,
arbitrum_sepolia,
astar,
avalanche,
b3,
base,
base_sepolia,
beacon,
beacon_validators,
berachain,
binance,
bitcoin,
blast,
bsc,
celo,
cosmos,
cosmoshub,
ethereum,
stellar,
ethereum_goerli,
fantom,
xrp_ledger,
vana,
dydx,
ethereum_sepolia,
kava,
bitcoin_cash,
celestia,
codex,
litecoin,
mantra,
dymension,
babylon,
ethereum_hoodi,
winr,
sx,
injective,
educhain,
dogecoin,
hyperevm,
hyperliquid,
everclear,
fraxtal,
gnosis,
gravity,
harmony,
hedera,
holesky,
imx_zkevm,
ink,
kinto,
linea,
manta_pacific,
mantle,
metis,
mode,
monad_devnet1,
monad_testnet,
near,
oasys,
optimism,
osmosis,
polygon,
polygon_zkevm,
proof_of_play_apex,
proof_of_play_boss,
provenance,
real,
reya,
ronin,
rootstock,
sanko,
scroll,
scroll_sepolia,
sei,
solana,
soneium,
sonic,
stacks,
starknet,
superposition,
sui,
ton,
tron,
unichain,
worldchain,
zksync,
zora
​
transaction_hash
string
required

Query Parameters

​
include_label
boolean
default:true

Response

200
application/json

Successful Response

The response is of type object.