← previous blocknext block →recent activity
Analyzing
Block #86,850,549
32 transactions · 25 stateful · 2026-07-10 13:48:41 UTC
Parallelism
84/100
Blocked
56%
Avg conflicts / tx
1.13
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,850,549 · 32 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
1w02w13w24w35w47w08w19w210w317w318w320w431w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf81d0d0f…cf78
0x34b655…2a6f
10 touches
10 conflicts
0xbcdee322…f454
0xa6afd3…d132
10 touches
10 conflicts
0x17c44db3…8888
0xa6afd3…d132
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0x0660fb83…44f9
0xd32edf…ff58
9 touches
10 conflicts
0x826cce18…251c
0x34b655…2a6f
8 touches
6 conflicts
0x071e17d4…fd91
0x34b655…2a6f
8 touches
6 conflicts
0x2b268fa9…eba2
0x34b655…2a6f
8 touches
6 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
10 conflicts on slot 0xf81d0d0f79…09cf78
Audit this contract →
← previous block·next block →recent activity