← previous blocknext block →recent activity
Analyzing
Block #88,343,163
17 transactions · 16 stateful · 2026-07-17 12:11:44 UTC
Parallelism
59/100
Blocked
50%
Avg conflicts / tx
1.24
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #88,343,163 · 17 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w16w27w39w410w512w615w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x427d1120…4eb1
0x34b655…2a6f
8 touches
6 conflicts
0xebc9f918…9f11
0x34b655…2a6f
8 touches
6 conflicts
0xc9dce17a…a1a1
0x34b655…2a6f
8 touches
6 conflicts
0x714420ba…96c5
0x34b655…2a6f
6 touches
3 conflicts
0x793aa64d…b09c
0x34b655…2a6f
4 touches
1 conflict
0x793aa64d…b09d
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
15 conflicts on slot 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity