← previous blocknext block →recent activity
Analyzing
Block #86,835,629
24 transactions · 19 stateful · 2026-07-10 12:09:01 UTC
Parallelism
79/100
Blocked
47%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,835,629 · 24 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
4w05w16w27w38w014w115w216w317w421w022w123w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3483ab79…8ed3
0x34b655…2a6f
10 touches
10 conflicts
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0x63c900f4…2600
0x34b655…2a6f
10 touches
10 conflicts
0x737acb78…fce8
0x34b655…2a6f
8 touches
6 conflicts
0x7523ad90…2ba5
0x34b655…2a6f
8 touches
6 conflicts
0x7e119210…ca8f
0x34b655…2a6f
8 touches
6 conflicts
0x03fb27fd…0c06
0x34b655…2a6f
8 touches
6 conflicts
0x14e7d4c1…2c28
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 0x3483ab79f0…398ed3
Audit this contract →
← previous block·next block →recent activity