← previous blocknext block →recent activity
Analyzing
Block #87,131,649
20 transactions · 20 stateful · 2026-07-11 21:07:01 UTC
Parallelism
80/100
Blocked
35%
Avg conflicts / tx
0.7
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,131,649 · 20 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
1w02w13w24w38w09w110w213w316w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x06aed19e…ca57
0x34b655…2a6f
8 touches
6 conflicts
0x2023631d…253a
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x25c9408f…62d5
0x34b655…2a6f
8 touches
6 conflicts
0x434eae6f…ffca
0x34b655…2a6f
8 touches
6 conflicts
0x49a819aa…8597
0x34b655…2a6f
8 touches
6 conflicts
0x5748450a…816f
0x34b655…2a6f
8 touches
6 conflicts
0x6608328c…bf07
0x34b655…2a6f
8 touches
6 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
6 conflicts on slot 0x06aed19eee…1cca57
Audit this contract →
← previous block·next block →recent activity