← previous blocknext block →recent activity
Analyzing
Block #87,689,621
23 transactions · 23 stateful · 2026-07-14 11:19:31 UTC
Parallelism
65/100
Blocked
48%
Avg conflicts / tx
1.13
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,689,621 · 23 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w27w38w49w510w613w214w317w118w422w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0x00d60c65…745d
0x34b655…2a6f
8 touches
6 conflicts
0x38948e75…437a
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x15bb0662…b802
0x34b655…2a6f
6 touches
3 conflicts
0xee06e767…00d6
0x34b655…2a6f
6 touches
3 conflicts
0xb4b8c5b1…836b
0x34b655…2a6f
6 touches
3 conflicts
0x1716b13d…99cc
0xc8689a…ee79
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
15 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity