← previous blocknext block →recent activity
Analyzing
Block #87,283,656
12 transactions · 11 stateful · 2026-07-12 14:04:07 UTC
Parallelism
67/100
Blocked
45%
Avg conflicts / tx
0.75
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,283,656 · 12 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
1w04w05w16w27w38w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x0dd44476…ef40
0x34b655…2a6f
6 touches
3 conflicts
0x226e3b61…5e6f
0x34b655…2a6f
6 touches
3 conflicts
0x625d2aaf…d28a
0x34b655…2a6f
6 touches
3 conflicts
0x70d66bd9…0ffa
0x34b655…2a6f
6 touches
3 conflicts
0x97befef4…9ba1
0x34b655…2a6f
5 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 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity