← previous blocknext block →recent activity
Analyzing
Block #89,516,735
28 transactions · 24 stateful · 2026-07-22 23:00:01 UTC
Parallelism
89/100
Blocked
33%
Avg conflicts / tx
0.46
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,516,735 · 28 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w211w012w113w114w115w216w221w025w027w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x06e40499…165e
0x2b46c0…1669
4 touches
1 conflict
0xa605468c…1bfc
0x2b46c0…1669
4 touches
1 conflict
0x178fe051…465a
0x34b655…2a6f
4 touches
1 conflict
0x327c57dd…836d
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity