← previous blocknext block →recent activity
Analyzing
Block #86,988,272
20 transactions · 20 stateful · 2026-07-11 05:09:15 UTC
Parallelism
70/100
Blocked
40%
Avg conflicts / tx
0.9
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,988,272 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w07w18w211w012w013w114w315w416w518w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xf29e5320…ce2d
0x34b655…2a6f
6 touches
3 conflicts
0x35d95fb0…db9f
0x34b655…2a6f
6 touches
3 conflicts
0x7e7de6d7…48be
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0xfa667abe…bdfc
0x34b655…2a6f
6 touches
3 conflicts
0x35d95fb0…db9e
0x34b655…2a6f
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
10 conflicts on slot 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity