← previous blocknext block →recent activity
Analyzing
Block #88,355,162
21 transactions · 17 stateful · 2026-07-17 13:32:08 UTC
Parallelism
71/100
Blocked
35%
Avg conflicts / tx
0.38
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #88,355,162 · 21 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
3w012w113w214w218w319w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0f6aef87…8137
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xf565ea1f…4245
0x34b655…2a6f
4 touches
1 conflict
0xfc48137a…510e
0x34b655…2a6f
4 touches
1 conflict
0x538f26af…0f39
0x34b655…2a6f
4 touches
1 conflict
0xebac0f82…a49c
0x34b655…2a6f
4 touches
1 conflict
0x56153262…21ce
0x34b655…2a6f
4 touches
1 conflict
0x3aea32bb…1ff5
0x34b655…2a6f
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
3 conflicts on slot 0x0f6aef8771…dd8137
Audit this contract →
← previous block·next block →recent activity