← previous blocknext block →recent activity
Analyzing
Block #88,364,031
19 transactions · 19 stateful · 2026-07-17 14:31:58 UTC
Parallelism
79/100
Blocked
32%
Avg conflicts / tx
0.37
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #88,364,031 · 19 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w18w111w212w316w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x063b8a70…7825
0x34b655…2a6f
4 touches
1 conflict
0x168a3739…d5c9
0x34b655…2a6f
4 touches
1 conflict
0x258fcaf5…2084
0x34b655…2a6f
4 touches
1 conflict
0x330df1e6…7587
0x34b655…2a6f
4 touches
1 conflict
0x3ef0952c…762d
0x34b655…2a6f
4 touches
1 conflict
0x427f51fd…bd80
0x34b655…2a6f
4 touches
1 conflict
0x59829278…9be0
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 0x737acb7813…fafce8
Audit this contract →
← previous block·next block →recent activity