← previous blocknext block →recent activity
Analyzing
Block #88,359,201
21 transactions · 19 stateful · 2026-07-17 13:59:29 UTC
Parallelism
67/100
Blocked
58%
Avg conflicts / tx
1.05
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #88,359,201 · 21 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
1w04w05w17w08w19w211w212w313w415w516w118w319w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa5a8ffca…8de2
0x34b655…2a6f
8 touches
6 conflicts
0x1e166a45…98a7
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x72abd523…d673
0x34b655…2a6f
4 touches
1 conflict
0xa55c4598…2988
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 0xa5a8ffca31…818de2
Audit this contract →
← previous block·next block →recent activity