← previous blocknext block →recent activity
Analyzing
Block #89,572,425
14 transactions · 14 stateful · 2026-07-23 05:12:01 UTC
Parallelism
57/100
Blocked
43%
Avg conflicts / tx
0.5
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #89,572,425 · 14 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w06w18w210w311w412w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x0da23f3d…0c13
0x34b655…2a6f
4 touches
1 conflict
0x114324a9…6d5e
0x34b655…2a6f
4 touches
1 conflict
0x43e3eaa8…ca16
0x34b655…2a6f
4 touches
1 conflict
0x43e3eaa8…ca17
0x34b655…2a6f
4 touches
1 conflict
0x5af10b50…8d5c
0x34b655…2a6f
4 touches
1 conflict
0x64aaadbf…f9f3
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity