← previous blocknext block →recent activity
Analyzing
Block #86,824,166
22 transactions · 20 stateful · 2026-07-10 10:52:23 UTC
Parallelism
64/100
Blocked
40%
Avg conflicts / tx
1.18
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,824,166 · 22 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w111w212w313w414w515w616w620w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x55625899…9074
0x34b655…2a6f
12 touches
15 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x0f4cddfd…3085
0x34b655…2a6f
10 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6426
0x34b655…2a6f
6 touches
3 conflicts
0x321dd53a…4aa4
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x5104991c…f259
0x34b655…2a6f
6 touches
3 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
15 conflicts on slot 0x55625899ba…5b9074
Audit this contract →
← previous block·next block →recent activity