← previous blocknext block →recent activity
Analyzing
Block #87,724,670
15 transactions · 14 stateful · 2026-07-14 15:14:19 UTC
Parallelism
47/100
Blocked
50%
Avg conflicts / tx
1.8
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,724,670 · 15 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
1w05w16w28w39w411w512w614w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0dd44476…ef40
0x34b655…2a6f
14 touches
21 conflicts
0x80fd3987…2314
0x34b655…2a6f
10 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x0c20b123…6e84
0x34b655…2a6f
8 touches
6 conflicts
0x64a058c6…74a1
0x34b655…2a6f
8 touches
6 conflicts
0x4cdf55e1…0f2d
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
21 conflicts on slot 0x0dd44476b8…7fef40
Audit this contract →
← previous block·next block →recent activity