← previous blocknext block →recent activity
Analyzing
Block #88,093,573
21 transactions · 20 stateful · 2026-07-16 08:21:48 UTC
Parallelism
81/100
Blocked
45%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #88,093,573 · 21 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
1w02w13w04w15w06w07w19w110w212w316w219w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9465204c…bf37
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0x04fdea…47d7
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x2a00a910…f960
0x34b655…2a6f
4 touches
1 conflict
0x366c7d57…0ed1
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4b5dd6bc…38e4
0x34b655…2a6f
4 touches
1 conflict
0x5c2c4b74…1748
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 0x9465204cd8…debf37
Audit this contract →
← previous block·next block →recent activity