← previous blocknext block →recent activity
Analyzing
Block #87,791,434
15 transactions · 13 stateful · 2026-07-14 22:40:57 UTC
Parallelism
80/100
Blocked
31%
Avg conflicts / tx
0.6
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,791,434 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w07w18w011w214w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8d989c17…e984
0x34b655…2a6f
6 touches
3 conflicts
0x1941b441…5889
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x2b95e778…d7d0
0x34b655…2a6f
6 touches
3 conflicts
0x5b145de0…367c
0xc8689a…ee79
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x28c62bca…b746
0x34b655…2a6f
4 touches
1 conflict
0x77d44e71…baa8
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
3 conflicts on slot 0x8d989c177f…b7e984
Audit this contract →
← previous block·next block →recent activity