← previous blocknext block →recent activity
Analyzing
Block #86,656,157
11 transactions · 9 stateful · 2026-07-09 16:10:10 UTC
Parallelism
82/100
Blocked
22%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,656,157 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdec4fb9a…1d0c
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x145b9bbf…e50e
0x34b655…2a6f
2 touches
0 conflicts
0x145b9bbf…e50f
0x34b655…2a6f
2 touches
0 conflicts
0x211d520a…bf67
0x34b655…2a6f
2 touches
0 conflicts
0x2ae0b4dc…6c9e
0x34b655…2a6f
2 touches
0 conflicts
0x68c07cb9…ae14
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xdec4fb9ac9…ce1d0c
Audit this contract →
← previous block·next block →recent activity