← previous blocknext block →recent activity
Analyzing
Block #86,813,522
15 transactions · 13 stateful · 2026-07-10 09:41:01 UTC
Parallelism
80/100
Blocked
31%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,813,522 · 15 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
4w07w18w212w013w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00873542…6db6
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x26054cbe…47df
0x34b655…2a6f
4 touches
1 conflict
0x6b899aa5…a7a6
0x34b655…2a6f
4 touches
1 conflict
0x86f32276…0ebf
0x34b655…2a6f
4 touches
1 conflict
0x8db5666d…76f0
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 0x00873542d7…d96db6
Audit this contract →
← previous block·next block →recent activity