← previous blocknext block →recent activity
Analyzing
Block #89,541,920
14 transactions · 13 stateful · 2026-07-23 01:48:10 UTC
Parallelism
64/100
Blocked
38%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #89,541,920 · 14 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
2w06w07w110w111w212w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x2ee5c07b…7eb9
0x34b655…2a6f
6 touches
3 conflicts
0x6e0e8837…2e59
0x34b655…2a6f
6 touches
3 conflicts
0xd1a8b9bd…6f8c
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x52f8fac1…8d8f
0x34b655…2a6f
4 touches
1 conflict
0x67f87cdf…e5b6
0x34b655…2a6f
4 touches
1 conflict
0x69d0a300…67ef
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity