← previous blocknext block →recent activity
Analyzing
Block #85,351,952
30 transactions · 22 stateful · 2026-07-03 15:06:38 UTC
Parallelism
93/100
Blocked
9%
Avg conflicts / tx
0.07
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,351,952 · 30 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
22w023w128w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x5636ef5b…c11d
0x34b655…2a6f
4 touches
1 conflict
0xd5dbfacf…c5ec
0x34b655…2a6f
4 touches
1 conflict
0xa4d876a6…5590
0x065c9d…c394
2 touches
0 conflicts
0x00f7e3b7…e015
0x188d58…ea8e
2 touches
0 conflicts
0x00f7e3b7…e016
0x188d58…ea8e
2 touches
0 conflicts
0x474fcc62…87fe
0x188d58…ea8e
2 touches
0 conflicts
0x474fcc62…87ff
0x188d58…ea8e
2 touches
0 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
1 conflict on slot 0xec7d120df9…5d7084
Audit this contract →
← previous block·next block →recent activity