← previous blocknext block →recent activity
Analyzing
Block #87,726,267
22 transactions · 21 stateful · 2026-07-14 15:25:00 UTC
Parallelism
55/100
Blocked
71%
Avg conflicts / tx
2
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #87,726,267 · 22 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w16w27w38w49w510w611w114w315w421w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
14 touches
21 conflicts
0x0dd44476…ef40
0x34b655…2a6f
10 touches
10 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0xc4de6652…13f4
0x34b655…2a6f
8 touches
6 conflicts
0x5b145de0…367c
0xc8689a…ee79
6 touches
3 conflicts
0x22e7ebfe…1293
0x34b655…2a6f
6 touches
3 conflicts
0x3034d073…89bb
0x34b655…2a6f
6 touches
3 conflicts
0x58620f29…db5a
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
21 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity