← previous blocknext block →recent activity
Analyzing
Block #87,517,018
23 transactions · 21 stateful · 2026-07-13 16:04:50 UTC
Parallelism
83/100
Blocked
33%
Avg conflicts / tx
0.7
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,517,018 · 23 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w07w18w29w313w014w115w217w320w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x99ee776a…053a
0x34b655…2a6f
8 touches
6 conflicts
0x0f068b13…fb19
0x34b655…2a6f
8 touches
6 conflicts
0x3cc30f15…223b
0x34b655…2a6f
6 touches
3 conflicts
0x63c900f4…2600
0x34b655…2a6f
6 touches
3 conflicts
0x96bfa04d…d06b
0x34b655…2a6f
6 touches
3 conflicts
0x5170a218…3a84
0xc8689a…ee79
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
6 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity