← previous blocknext block →recent activity
Analyzing
Block #88,185,741
17 transactions · 16 stateful · 2026-07-16 18:39:04 UTC
Parallelism
71/100
Blocked
31%
Avg conflicts / tx
0.47
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #88,185,741 · 17 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
2w03w04w17w08w110w011w212w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4b80417b…75c3
0x34b655…2a6f
6 touches
3 conflicts
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0x0b0c2e8d…c1b8
0xe52b14…7230
4 touches
1 conflict
0x532023a5…d800
0xe52b14…7230
4 touches
1 conflict
0x8ffa3328…ce11
0xe52b14…7230
4 touches
1 conflict
0x44fb0f8a…b7c3
0x34b655…2a6f
4 touches
1 conflict
0x44fb0f8a…b7c4
0x34b655…2a6f
4 touches
1 conflict
0x52a2ba74…f2f7
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
3 conflicts on slot 0x4b80417b65…f875c3
Audit this contract →
← previous block·next block →recent activity