← previous blocknext block →recent activity
Analyzing
Block #88,358,230
14 transactions · 13 stateful · 2026-07-17 13:52:58 UTC
Parallelism
57/100
Blocked
38%
Avg conflicts / tx
0.57
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #88,358,230 · 14 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w37w48w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xafd867b7…2b2d
0x34b655…2a6f
4 touches
1 conflict
0xc4de6652…13f4
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x8e9e558d…aa92
0x34b655…2a6f
3 touches
1 conflict
0x55012d1a…3907
0x2b46c0…1669
2 touches
0 conflicts
0x8b8c3b8a…9b6a
0x2b46c0…1669
2 touches
0 conflicts
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
6 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity