← previous blocknext block →recent activity
Analyzing
Block #111,843,251
25 transactions · 21 stateful · 2026-10-09 08:01:55 UTC
Parallelism
88/100
Blocked
14%
Avg conflicts / tx
0.16
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #111,843,251 · 25 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w07w014w115w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4f363b3a…4b87
0x34b655…2a6f
4 touches
1 conflict
0x00000000…002f
0x1b6862…e19c
4 touches
1 conflict
0x7954ece9…fef0
0x34b655…2a6f
4 touches
1 conflict
0x6235638c…643d
0x1b6862…e19c
4 touches
1 conflict
0xd9e81bdd…b6a9
0x34b655…2a6f
4 touches
1 conflict
0xfdd40e24…dca0
0x34b655…2a6f
4 touches
1 conflict
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
0xcb45d9d6…cb87
0x1b6862…e19c
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
1 conflict on slot 0x4f363b3a02…5c4b87
Audit this contract →
← previous block·next block →recent activity