← previous blocknext block →recent activity
Analyzing
Block #88,340,720
13 transactions · 12 stateful · 2026-07-17 11:55:24 UTC
Parallelism
77/100
Blocked
33%
Avg conflicts / tx
0.54
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #88,340,720 · 13 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
2w04w05w16w29w010w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6eb3e5af…064e
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xf1345bef…5530
0x34b655…2a6f
6 touches
3 conflicts
0x35cfae1b…c1f8
0x34b655…2a6f
4 touches
1 conflict
0x56f678c0…4f9c
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x7c6cfc14…9957
0x34b655…2a6f
4 touches
1 conflict
0x7c6cfc14…9958
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 0x6eb3e5af4f…78064e
Audit this contract →
← previous block·next block →recent activity