← previous blocknext block →recent activity
Analyzing
Block #86,837,966
35 transactions · 24 stateful · 2026-07-10 12:24:38 UTC
Parallelism
86/100
Blocked
42%
Avg conflicts / tx
0.49
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,837,966 · 35 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w07w08w112w114w015w119w020w121w222w324w225w327w328w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x94ba9c4a…41d8
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x54b25a61…16ce
0xd32edf…ff58
5 touches
3 conflicts
0x4b8b3363…6633
0x34b655…2a6f
4 touches
1 conflict
0x4ba9d297…f0be
0x34b655…2a6f
4 touches
1 conflict
0x574c00dc…ea37
0x34b655…2a6f
4 touches
1 conflict
0x574c00dc…ea38
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
3 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity