← previous blocknext block →recent activity
Analyzing
Block #87,621,263
24 transactions · 20 stateful · 2026-07-14 03:42:39 UTC
Parallelism
83/100
Blocked
55%
Avg conflicts / tx
0.79
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,621,263 · 24 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
1w02w13w25w18w09w110w212w014w115w216w217w018w119w222w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc9fe0433…7f01
0x34b655…2a6f
8 touches
6 conflicts
0xd64c1971…1bf2
0x34b655…2a6f
8 touches
6 conflicts
0x18e900fa…07f4
0x34b655…2a6f
6 touches
3 conflicts
0x25329a48…4e00
0x34b655…2a6f
6 touches
3 conflicts
0x5170a218…3a84
0xc8689a…ee79
6 touches
3 conflicts
0x3f17ba84…aa87
0x34b655…2a6f
6 touches
3 conflicts
0x68b75835…d6f3
0x34b655…2a6f
6 touches
3 conflicts
0xd379a368…fea4
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
6 conflicts on slot 0xc9fe0433ca…417f01
Audit this contract →
← previous block·next block →recent activity