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 at the same time due to a bug or a malicious attack.
Supported Protocols
bitcoin/mainnet
bitcoin/testnet
bitcoincash/mainnet
dogecoin/mainnet
ethereum/mainnet
ethereum/holesky
litecoin/mainnet
polkadot/mainnet
polkadot/westend
polygon/mainnet
polygon/amoy
Schema
{
"data": {
"block_number": "integer",
"block_hash": "string",
"block_timestamp": "integer"
}
}
The table below shows the schema breakdown:
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. |
Examples
Polkadot Example
{
"protocol": "polkadot",
"network": "mainnet",
"event_type": "unified_reorg",
"chain_id":"polkadot:91b171bb158e2d3848fa23a9f1c25182",
"data": {
"block_number": 19583058,
"block_hash": "0x5763259919f255eb0330a9820182edabe42e5de4297ad7b49824f9a591d8a8a8",
"block_timestamp": 1708529886
}
}
Dogecoin Example
{
"protocol": "dogecoin",
"network": "mainnet",
"event_type": "unified_reorg",
"chain_id": "bip122:1a91e3dace36e2be3bf030a65679fe82",
"data": {
"block_hash": "0000000000000000000278b53131091627eaa00f772f3c7b2a59c374666520d7",
"block_number": 831663,
"block_timestamp": 1708679008
}
}
Bitcoin Example
{
"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.