← previous blocknext block →recent activity
Analyzing
Block #88,357,859
21 transactions · 17 stateful · 2026-07-17 13:50:29 UTC
Parallelism
76/100
Blocked
29%
Avg conflicts / tx
0.43
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #88,357,859 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w011w012w113w115w219w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc9dce17a…a1a1
0x34b655…2a6f
8 touches
6 conflicts
0xe5a9274d…78d7
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x09edbcde…e50d
0x34b655…2a6f
4 touches
1 conflict
0x0a5937e1…ccdd
0x34b655…2a6f
4 touches
1 conflict
0x1d0eccac…614b
0x34b655…2a6f
4 touches
1 conflict
0x367b69ad…33d8
0x34b655…2a6f
4 touches
1 conflict
0x367b69ad…33d9
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
6 conflicts on slot 0xc9dce17a10…8ca1a1
Audit this contract →
← previous block·next block →recent activity