← previous blocknext block →recent activity
Analyzing
Block #86,767,051
35 transactions · 18 stateful · 2026-07-10 04:30:42 UTC
Parallelism
89/100
Blocked
44%
Avg conflicts / tx
0.34
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,767,051 · 35 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
1w03w04w111w112w217w020w022w024w225w128w130w333w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x3e6563f1…1c23
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x89750670…2dea
0xa6afd3…d132
6 touches
3 conflicts
0x48d5f867…0d57
0xd32edf…ff58
5 touches
3 conflicts
0x7584bc06…3463
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x8b8c3b8a…9b6a
0x69df8a…6292
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