← previous blocknext block →recent activity
Analyzing
Block #87,710,730
23 transactions · 22 stateful · 2026-07-14 13:40:55 UTC
Parallelism
70/100
Blocked
41%
Avg conflicts / tx
1.26
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,710,730 · 23 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w28w312w213w315w417w519w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
10 touches
10 conflicts
0x64aaadbf…f9f3
0x34b655…2a6f
10 touches
10 conflicts
0x0f6666e6…f280
0x34b655…2a6f
8 touches
6 conflicts
0xebda63e5…9238
0x34b655…2a6f
6 touches
3 conflicts
0xaf669096…ecf9
0x34b655…2a6f
6 touches
3 conflicts
0xaba6578d…bd48
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity