← previous blocknext block →recent activity
Analyzing
Block #87,761,049
18 transactions · 17 stateful · 2026-07-14 19:17:39 UTC
Parallelism
67/100
Blocked
41%
Avg conflicts / tx
1.06
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,761,049 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w38w49w513w416w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
12 touches
15 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
12 touches
15 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0x313d3d93…4aa2
0x34b655…2a6f
6 touches
3 conflicts
0xa0a5bed4…1d15
0x34b655…2a6f
6 touches
3 conflicts
0xa38eb2fc…1659
0x34b655…2a6f
6 touches
3 conflicts
0x6254804c…a03c
0x34b655…2a6f
4 touches
1 conflict
0x367b69ad…33d9
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
15 conflicts on slot 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity