← previous blocknext block →recent activity
Analyzing
Block #87,735,133
21 transactions · 19 stateful · 2026-07-14 16:24:18 UTC
Parallelism
57/100
Blocked
47%
Avg conflicts / tx
1.43
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #87,735,133 · 21 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w38w49w510w611w716w819w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9001f549…089d
0x34b655…2a6f
10 touches
10 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
10 touches
10 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x5597fdd8…3f39
0x34b655…2a6f
6 touches
3 conflicts
0x58620f29…db5a
0x34b655…2a6f
6 touches
3 conflicts
0x5e4b65e1…ebe1
0x34b655…2a6f
6 touches
3 conflicts
0x64aaadbf…f9f3
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
10 conflicts on slot 0x9001f5497d…54089d
Audit this contract →
← previous block·next block →recent activity