← previous blocknext block →recent activity
Analyzing
Block #86,815,295
19 transactions · 19 stateful · 2026-07-10 09:52:53 UTC
Parallelism
74/100
Blocked
26%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,815,295 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w06w110w212w313w415w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x55642f63…03d6
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x89c4fedf…b214
0x34b655…2a6f
6 touches
3 conflicts
0xdb89ef9a…606c
0x34b655…2a6f
6 touches
3 conflicts
0x09500602…94ea
0x34b655…2a6f
4 touches
1 conflict
0x64a785e4…0110
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 0x55642f6368…8e03d6
Audit this contract →
← previous block·next block →recent activity