← previous blocknext block →recent activity
Analyzing
Block #86,340,991
13 transactions · 12 stateful · 2026-07-08 05:01:12 UTC
Parallelism
85/100
Blocked
8%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,340,991 · 13 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4bfdcd51…9b58
0x34b655…2a6f
4 touches
1 conflict
0xec0e0220…cb90
0x34b655…2a6f
4 touches
1 conflict
0x034f1f86…4e8d
0x34b655…2a6f
4 touches
1 conflict
0x02991b41…19e6
0x34b655…2a6f
4 touches
1 conflict
0x3ddd83da…7fb5
0x34b655…2a6f
4 touches
1 conflict
0xb0ce5883…746c
0x2a68ba…90c5
2 touches
0 conflicts
0x22e0cc1d…ad04
0x34b655…2a6f
2 touches
0 conflicts
0xf08e3681…09ce
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 0x4bfdcd5135…769b58
Audit this contract →
← previous block·next block →recent activity