← previous blocknext block →recent activity
Analyzing
Block #87,122,909
10 transactions · 9 stateful · 2026-07-11 20:08:38 UTC
Parallelism
60/100
Blocked
44%
Avg conflicts / tx
0.9
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,122,909 · 10 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w38w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc36fa358…24cb
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x98b248c3…9ea5
0x34b655…2a6f
8 touches
6 conflicts
0xdd38f4e6…586c
0x34b655…2a6f
6 touches
3 conflicts
0xdd38f4e6…586d
0x34b655…2a6f
6 touches
3 conflicts
0x619c81de…01b4
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x9509e5ec…7029
0x34b655…2a6f
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
6 conflicts on slot 0xc36fa35805…6f24cb
Audit this contract →
← previous block·next block →recent activity