← previous blocknext block →recent activity
Analyzing
Block #88,078,052
22 transactions · 21 stateful · 2026-07-16 06:37:59 UTC
Parallelism
77/100
Blocked
62%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #88,078,052 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w27w38w411w214w115w217w318w220w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xcc351d6d…256b
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x36385a2d…35f8
0x34b655…2a6f
4 touches
1 conflict
0x4f647bcf…b0cd
0x34b655…2a6f
4 touches
1 conflict
0x5777bd87…71bd
0x34b655…2a6f
4 touches
1 conflict
0x5af10b50…8d5c
0x34b655…2a6f
4 touches
1 conflict
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
10 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity