← previous blocknext block →recent activity
Analyzing
Block #86,305,196
19 transactions · 14 stateful · 2026-07-08 01:02:01 UTC
Parallelism
84/100
Blocked
36%
Avg conflicts / tx
0.42
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,305,196 · 19 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w110w212w014w015w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7c37629d…9e3f
0x34b655…2a6f
6 touches
3 conflicts
0x2c2761c0…476e
0x34b655…2a6f
6 touches
3 conflicts
0x966e45cf…0f25
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x298155aa…b111
0x34b655…2a6f
4 touches
1 conflict
0x43e3decb…be40
0x34b655…2a6f
4 touches
1 conflict
0x47da8843…9ce1
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
3 conflicts on slot 0x7c37629d56…dd9e3f
Audit this contract →
← previous block·next block →recent activity