← previous blocknext block →recent activity
Analyzing
Block #86,664,754
28 transactions · 27 stateful · 2026-07-09 17:07:33 UTC
Parallelism
86/100
Blocked
63%
Avg conflicts / tx
1.04
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,664,754 · 28 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
1w02w13w24w35w07w18w19w210w011w112w213w316w118w220w121w222w223w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x862487f4…d5df
0x065c9d…c394
7 touches
6 conflicts
0xb1708b38…feb7
0xd32edf…ff58
7 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x1941b441…5889
0x34b655…2a6f
6 touches
3 conflicts
0x17606ba6…1b6e
0x754704…b603
6 touches
3 conflicts
0x8a35acfb…d1ab
0xb1dbf0…c0d3
6 touches
3 conflicts
0x8a35acfb…d1ac
0xb1dbf0…c0d3
6 touches
3 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
6 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity