← previous blocknext block →recent activity
Analyzing
Block #87,724,112
40 transactions · 33 stateful · 2026-07-14 15:10:35 UTC
Parallelism
82/100
Blocked
48%
Avg conflicts / tx
1.02
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,724,112 · 40 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w111w112w213w314w415w516w017w118w223w325w426w227w132w539w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x0733be30…112f
0x34b655…2a6f
10 touches
10 conflicts
0xa0ebadea…4145
0x34b655…2a6f
8 touches
6 conflicts
0x79bdf655…91f2
0x34b655…2a6f
8 touches
6 conflicts
0xffc2f21e…b393
0x34b655…2a6f
6 touches
3 conflicts
0x40883ce5…2ae2
0x34b655…2a6f
6 touches
3 conflicts
0x5ec64628…72e4
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity