← previous blocknext block →recent activity
Analyzing
Block #87,879,651
30 transactions · 21 stateful · 2026-07-15 08:30:59 UTC
Parallelism
80/100
Blocked
29%
Avg conflicts / tx
0.33
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,879,651 · 30 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
2w06w07w111w212w315w416w117w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x88f37d98…6792
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4ab
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x25ff7717…d4af
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5ce8e9ad…6207
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
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
6 conflicts on slot 0x88f37d9873…476792
Audit this contract →
← previous block·next block →recent activity