← previous blocknext block →recent activity
Analyzing
Block #86,703,012
32 transactions · 22 stateful · 2026-07-09 21:22:50 UTC
Parallelism
88/100
Blocked
36%
Avg conflicts / tx
0.41
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,703,012 · 32 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
4w05w16w211w014w015w116w217w226w127w229w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xa7013be2…c0a8
0x34b655…2a6f
6 touches
3 conflicts
0xd35f2a86…8992
0xd32edf…ff58
5 touches
3 conflicts
0x916f2285…f095
0x34b655…2a6f
4 touches
1 conflict
0x916f2285…f096
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x953517cb…cdec
0x34b655…2a6f
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity