← previous blocknext block →recent activity
Analyzing
Block #87,311,778
11 transactions · 9 stateful · 2026-07-12 17:12:09 UTC
Parallelism
64/100
Blocked
33%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,311,778 · 11 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4a4
0x34b655…2a6f
6 touches
3 conflicts
0x799ee783…1f74
0x34b655…2a6f
6 touches
3 conflicts
0x1ed62880…5619
0x34b655…2a6f
4 touches
1 conflict
0x7d6e48e8…f2b5
0x34b655…2a6f
4 touches
1 conflict
0x7e1d87b8…291c
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4a2
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4a3
0x34b655…2a6f
4 touches
1 conflict
0xdabfb79d…d789
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 0x7e5ea60ab2…b0c4a4
Audit this contract →
← previous block·next block →recent activity