← previous blocknext block →recent activity
Analyzing
Block #88,364,723
20 transactions · 19 stateful · 2026-07-17 14:36:40 UTC
Parallelism
80/100
Blocked
42%
Avg conflicts / tx
0.7
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #88,364,723 · 20 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
1w02w13w06w07w18w111w012w113w216w218w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0006
0x0a2fbf…29b1
6 touches
3 conflicts
0x6ed0779d…19a6
0x0a2fbf…29b1
6 touches
3 conflicts
0x6ed0779d…19a7
0x0a2fbf…29b1
6 touches
3 conflicts
0xdc26b069…0bdf
0x0a2fbf…29b1
6 touches
3 conflicts
0xdc26b069…0be0
0x0a2fbf…29b1
6 touches
3 conflicts
0xdc26b069…0be3
0x0a2fbf…29b1
6 touches
3 conflicts
0x2d651956…12e8
0x34b655…2a6f
6 touches
3 conflicts
0x2f461725…5ab2
0x34b655…2a6f
6 touches
3 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: 0x0a2fbf2d…f729b1
3 conflicts on slot 0x0000000000…000006
Audit this contract →
← previous block·next block →recent activity