← previous blocknext block →recent activity
Analyzing
Block #86,835,918
18 transactions · 15 stateful · 2026-07-10 12:10:57 UTC
Parallelism
78/100
Blocked
40%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,835,918 · 18 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
1w04w05w16w08w19w210w315w016w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xa100c256…fb30
0x34b655…2a6f
6 touches
3 conflicts
0x199944d5…ab9f
0x34b655…2a6f
6 touches
3 conflicts
0x44485f70…b1ac
0x34b655…2a6f
4 touches
1 conflict
0x864a35d6…427f
0x34b655…2a6f
4 touches
1 conflict
0x864a35d6…4280
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