Unified Reorg
This event is triggered when a blockchain reorganization (reorg) occurs on a given chain. This can happen for several reasons, including:
- A different block replaces the latest block at the chain's height.
- Multiple blocks are produced simultaneously due to a bug or a malicious attack.
Supported Protocols
base/mainnetbase/sepoliabitcoin/mainnetbitcoin/testnetbitcoin/testnet4bitcoincash/mainnetbitcoincash/testnetbnb/mainnetbnb/testnetdogecoin/mainnetdogecoin/testnetethereum/mainnetethereum/sepoliaethereum/hoodikaia/mainnetkaia/testnetlitecoin/mainnetlitecoin/testnetmonad/mainnetmonad/testnetpolkadot/mainnetpolkadot/westendpolygon/mainnetpolygon/amoytron/mainnettron/nile
Schema
{
"data": {
"block_number": "integer",
"block_hash": "string",
"block_timestamp": "integer"
}
}| Field | Type | Description |
|---|---|---|
block_hash | string | (Required) The block hash. |
block_number | integer | (Required) The block number. |
block_timestamp | integer | (Required) The UNIX timestamp when the block was mined/validated. |
This schema applies to the UNIFIED_V1 and UNIFIED_V1_RAW templates. ALL_DATA returns the chain's native reorg payload unmodified, with its own fields, shown below per protocol.
InfoBase, BNB Smart Chain, Ethereum, Kaia, Litecoin, Monad, Polygon, and Tron aren't shown in the picker below yet. They're supported for this event type, but a payload example hasn't been captured for them.
Examples
Bitcoin
Bitcoin's native reorg notification already matches the unified schema field-for-field, so ALL_DATA and UNIFIED_V1 are identical for this protocol.
{
"protocol": "bitcoin",
"network": "mainnet",
"event_type": "unified_reorg",
"chain_id": "bip122:000000000019d6689c085ae165831e93",
"data": {
"block_hash": "0000000000000000000278b53131091627eaa00f772f3c7b2a59c374666520d7",
"block_number": 831663,
"block_timestamp": 1708679008
}
}👋 Need Help?
Contact us through email or our support page for any issues, bugs, or assistance you may need.
Updated 3 days ago
