← previous blocknext block →recent activity
Analyzing
Block #87,123,055
11 transactions · 9 stateful · 2026-07-11 20:09:36 UTC
Parallelism
82/100
Blocked
22%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,123,055 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w16w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa08f40b2…9a93
0x34b655…2a6f
4 touches
1 conflict
0xe4b8f2c5…f54d
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x313d3d93…4aa2
0x34b655…2a6f
4 touches
1 conflict
0x15c87186…886d
0xd32edf…ff58
3 touches
1 conflict
0x16649a8b…40b1
0x34b655…2a6f
2 touches
0 conflicts
0x2003d8cf…6836
0x34b655…2a6f
2 touches
0 conflicts
0x33f96819…9222
0x34b655…2a6f
2 touches
0 conflicts
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 0xa08f40b255…099a93
Audit this contract →
← previous block·next block →recent activity