← previous blocknext block →recent activity
Analyzing
Block #86,712,212
15 transactions · 11 stateful · 2026-07-09 22:24:13 UTC
Parallelism
60/100
Blocked
55%
Avg conflicts / tx
0.87
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,712,212 · 15 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w26w37w48w514w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x8b87ece6…3353
0x34b655…2a6f
6 touches
3 conflicts
0x148e7132…f2a4
0x34b655…2a6f
4 touches
1 conflict
0x1afc65c5…1f70
0x34b655…2a6f
4 touches
1 conflict
0x4ab0fef9…caef
0x34b655…2a6f
4 touches
1 conflict
0x55cd0be9…3712
0x34b655…2a6f
4 touches
1 conflict
0x57330c5d…9973
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
6 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity