← previous blocknext block →recent activity
Analyzing
Block #86,955,981
13 transactions · 12 stateful · 2026-07-11 01:33:29 UTC
Parallelism
77/100
Blocked
17%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,955,981 · 13 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
6w07w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x35d95fb0…db9e
0x34b655…2a6f
6 touches
3 conflicts
0x35d95fb0…db9f
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xf29e5320…ce2d
0x34b655…2a6f
6 touches
3 conflicts
0xb7d37f4e…67e4
0x34b655…2a6f
4 touches
2 conflicts
0xf424fd84…0ae0
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
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 0x35d95fb08d…29db9e
Audit this contract →
← previous block·next block →recent activity