← previous blocknext block →recent activity
Analyzing
Block #88,361,088
24 transactions · 23 stateful · 2026-07-17 14:12:11 UTC
Parallelism
67/100
Blocked
43%
Avg conflicts / tx
1.13
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #88,361,088 · 24 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w17w29w312w313w414w116w518w619w723w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x8252706a…7ca5
0x34b655…2a6f
10 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
10 touches
10 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xe2ca9bf2…8da8
0x34b655…2a6f
6 touches
3 conflicts
0xa5ab7b8a…c97b
0x34b655…2a6f
4 touches
1 conflict
0xa67622bd…42a1
0x34b655…2a6f
4 touches
1 conflict
0xb4e0c126…218f
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
10 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity