← previous blocknext block →recent activity
Analyzing
Block #86,340,213
10 transactions · 9 stateful · 2026-07-08 04:55:59 UTC
Parallelism
70/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,340,213 · 10 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
5w07w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa8b18ba0…f380
0x34b655…2a6f
4 touches
1 conflict
0x7ea6a117…f2f2
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x7400926d…e46d
0x0c65a0…0852
2 touches
0 conflicts
0x034f1f86…4e8d
0x34b655…2a6f
2 touches
0 conflicts
0x07bb3f5a…617e
0x34b655…2a6f
2 touches
0 conflicts
0x29d3f69c…c4ab
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 0xa8b18ba0f2…07f380
Audit this contract →
← previous block·next block →recent activity