← previous blocknext block →recent activity
Analyzing
Block #89,761,180
11 transactions · 10 stateful · 2026-07-23 23:23:06 UTC
Parallelism
73/100
Blocked
20%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,761,180 · 11 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
2w03w14w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x81a169fb…d227
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x0a57a2b8…3cdd
0x34b655…2a6f
2 touches
0 conflicts
0x3ae2bbe1…fc45
0x34b655…2a6f
2 touches
0 conflicts
0x48f3c24c…f18a
0x34b655…2a6f
2 touches
0 conflicts
0x4ab0fef9…caef
0x34b655…2a6f
2 touches
0 conflicts
0x4ca81ae8…01d4
0x34b655…2a6f
2 touches
0 conflicts
0x4f267385…cc89
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0x81a169fb15…f9d227
Audit this contract →
← previous block·next block →recent activity