← previous blocknext block →recent activity
Analyzing
Block #86,609,195
14 transactions · 11 stateful · 2026-07-09 10:55:12 UTC
Parallelism
86/100
Blocked
18%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,609,195 · 14 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
2w06w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1cdfe548…d3aa
0x34b655…2a6f
4 touches
1 conflict
0xb4994d44…510f
0x34b655…2a6f
4 touches
1 conflict
0x5e782d17…5318
0x34b655…2a6f
4 touches
1 conflict
0x07bb3f5a…617e
0x34b655…2a6f
4 touches
1 conflict
0x09d9a46c…fc3d
0x34b655…2a6f
2 touches
0 conflicts
0x3be55cdc…2d19
0x34b655…2a6f
2 touches
0 conflicts
0x3cf50d44…961b
0x34b655…2a6f
2 touches
0 conflicts
0x57e6434c…aaaf
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 0x1cdfe54872…bcd3aa
Audit this contract →
← previous block·next block →recent activity