← previous blocknext block →recent activity
Analyzing
Block #88,092,808
26 transactions · 23 stateful · 2026-07-16 08:16:41 UTC
Parallelism
77/100
Blocked
30%
Avg conflicts / tx
0.38
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #88,092,808 · 26 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
1w08w09w110w214w120w021w322w423w524w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x04a566e1…26f3
0x34b655…2a6f
6 touches
3 conflicts
0xdb661970…3855
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xac6f24e7…c98b
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xf219f7cf…7379
0xa6afd3…d132
4 touches
1 conflict
0x08d66073…e706
0x34b655…2a6f
4 touches
1 conflict
0x3d8bb490…d81e
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 0x04a566e1fd…f826f3
Audit this contract →
← previous block·next block →recent activity