← previous blocknext block →recent activity
Analyzing
Block #87,588,584
21 transactions · 21 stateful · 2026-07-14 00:04:08 UTC
Parallelism
71/100
Blocked
48%
Avg conflicts / tx
1.05
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,588,584 · 21 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
2w03w14w25w36w47w510w011w112w015w217w119w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x18904470…0ef9
0x34b655…2a6f
12 touches
15 conflicts
0x34425c26…0709
0x34b655…2a6f
12 touches
15 conflicts
0x370e2c33…75b8
0x34b655…2a6f
12 touches
15 conflicts
0x63f8a50d…333b
0x34b655…2a6f
12 touches
15 conflicts
0x5170a218…3a84
0xc8689a…ee79
10 touches
10 conflicts
0x2e64e234…5cfa
0x34b655…2a6f
10 touches
10 conflicts
0x2f702750…347d
0x34b655…2a6f
10 touches
10 conflicts
0x63c900f4…2600
0x34b655…2a6f
10 touches
10 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
15 conflicts on slot 0x1890447084…300ef9
Audit this contract →
← previous block·next block →recent activity