← previous blocknext block →recent activity
Analyzing
Block #87,251,366
17 transactions · 17 stateful · 2026-07-12 10:28:13 UTC
Parallelism
65/100
Blocked
29%
Avg conflicts / tx
0.59
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,251,366 · 17 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
2w06w08w19w210w315w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0a0cecef…4ed0
0x34b655…2a6f
8 touches
6 conflicts
0xe2e21cdb…e6da
0x34b655…2a6f
6 touches
3 conflicts
0xa44c24a6…42f3
0x34b655…2a6f
6 touches
3 conflicts
0x51611059…097e
0x34b655…2a6f
4 touches
1 conflict
0x564b7fcf…deb4
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x793aa64d…b09c
0x34b655…2a6f
4 touches
1 conflict
0x793aa64d…b09d
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
6 conflicts on slot 0x0a0cecef55…324ed0
Audit this contract →
← previous block·next block →recent activity