← previous blocknext block →recent activity
Analyzing
Block #89,680,499
14 transactions · 13 stateful · 2026-07-23 16:35:55 UTC
Parallelism
64/100
Blocked
38%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #89,680,499 · 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
4w05w06w110w111w212w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xf1cc9519…84c1
0x34b655…2a6f
8 touches
6 conflicts
0x34a2c248…f7ed
0x34b655…2a6f
6 touches
3 conflicts
0xd70834dc…3797
0x34b655…2a6f
6 touches
3 conflicts
0xd9a771df…a27b
0x34b655…2a6f
6 touches
3 conflicts
0x3c7c65d0…0b52
0x34b655…2a6f
4 touches
1 conflict
0x3d0b31ee…7fa2
0x34b655…2a6f
4 touches
1 conflict
0x4755fafb…859b
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