← previous blocknext block →recent activity
Analyzing
Block #86,512,083
25 transactions · 24 stateful · 2026-07-09 00:04:19 UTC
Parallelism
84/100
Blocked
38%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,512,083 · 25 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w18w29w313w016w118w019w120w222w023w124w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x63c900f4…2600
0x34b655…2a6f
8 touches
6 conflicts
0x922c7ebd…6600
0xc8689a…ee79
8 touches
6 conflicts
0xf324b405…ca30
0x34b655…2a6f
8 touches
6 conflicts
0xb2945ca9…9ca5
0x34b655…2a6f
6 touches
3 conflicts
0x3483ab79…8ed3
0x34b655…2a6f
6 touches
3 conflicts
0x8bc992df…a233
0x34b655…2a6f
6 touches
3 conflicts
0xba559de1…6d2c
0x34b655…2a6f
6 touches
3 conflicts
0xcfa965cc…6fcf
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x63c900f479…962600
Audit this contract →
← previous block·next block →recent activity