← previous blocknext block →recent activity
Analyzing
Block #87,758,421
13 transactions · 8 stateful · 2026-07-14 19:00:04 UTC
Parallelism
77/100
Blocked
38%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,758,421 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w15w212w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x79277877…6098
0x34b655…2a6f
4 touches
1 conflict
0x0dd44476…ef40
0x34b655…2a6f
4 touches
1 conflict
0x2f35c56f…046b
0x34b655…2a6f
4 touches
1 conflict
0x1a6cdc0e…0af5
0x34b655…2a6f
2 touches
0 conflicts
0x2a67f3f5…5b31
0x34b655…2a6f
2 touches
0 conflicts
0x4cee015b…1a5e
0x34b655…2a6f
2 touches
0 conflicts
0x563ae507…382e
0x34b655…2a6f
2 touches
0 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
3 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity