← previous blocknext block →recent activity
Analyzing
Block #88,351,413
29 transactions · 23 stateful · 2026-07-17 13:06:58 UTC
Parallelism
83/100
Blocked
39%
Avg conflicts / tx
0.55
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #88,351,413 · 29 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
1w04w17w08w111w012w115w116w017w119w122w224w325w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x94e68337…5eb0
0x34b655…2a6f
8 touches
6 conflicts
0x6396a4c4…f626
0x34b655…2a6f
6 touches
3 conflicts
0xebac0f82…a49c
0x34b655…2a6f
6 touches
3 conflicts
0x27b9caf2…c102
0x34b655…2a6f
4 touches
1 conflict
0x3a7fb5b5…f0e5
0x34b655…2a6f
4 touches
1 conflict
0x65f773b6…46cc
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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 0x94e6833749…795eb0
Audit this contract →
← previous block·next block →recent activity