← previous blocknext block →recent activity
Analyzing
Block #88,183,686
15 transactions · 15 stateful · 2026-07-16 18:25:13 UTC
Parallelism
80/100
Blocked
27%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #88,183,686 · 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
1w05w16w27w212w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x103f3294…1abb
0x34b655…2a6f
4 touches
1 conflict
0x103f3294…1abc
0x34b655…2a6f
4 touches
1 conflict
0x403b061b…9f34
0x34b655…2a6f
4 touches
1 conflict
0x45070146…5c37
0x34b655…2a6f
4 touches
1 conflict
0x455a8076…be99
0x34b655…2a6f
4 touches
1 conflict
0x562a4a30…f8d5
0x34b655…2a6f
4 touches
1 conflict
0x6073e5e4…ddda
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 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity