← previous blocknext block →recent activity
Analyzing
Block #87,716,269
20 transactions · 20 stateful · 2026-07-14 14:18:05 UTC
Parallelism
75/100
Blocked
45%
Avg conflicts / tx
0.8
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,716,269 · 20 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
4w05w16w27w310w011w112w213w317w218w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xb11a3969…fc6a
0x34b655…2a6f
8 touches
6 conflicts
0x7c0bdc54…9dde
0x34b655…2a6f
8 touches
6 conflicts
0x5170a218…3a84
0xc8689a…ee79
8 touches
6 conflicts
0x5c3cb0f1…a9fa
0x34b655…2a6f
8 touches
6 conflicts
0x6432e978…c3ed
0x34b655…2a6f
8 touches
6 conflicts
0xad432af7…e34f
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
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
6 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity