← previous blocknext block →recent activity
Analyzing
Block #89,735,270
12 transactions · 11 stateful · 2026-07-23 21:12:15 UTC
Parallelism
67/100
Blocked
27%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,735,270 · 12 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w110w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc948dbdc…199a
0x34b655…2a6f
8 touches
6 conflicts
0x09dddc76…e12a
0x34b655…2a6f
6 touches
3 conflicts
0x560b6fd9…a104
0x34b655…2a6f
6 touches
3 conflicts
0x648bb928…97f2
0x34b655…2a6f
6 touches
3 conflicts
0x364289f7…f98a
0x34b655…2a6f
4 touches
1 conflict
0x3837ae12…6c37
0x34b655…2a6f
4 touches
1 conflict
0x3e2663d3…a620
0x34b655…2a6f
4 touches
1 conflict
0x3f3d0666…5614
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 0xc948dbdcb8…f4199a
Audit this contract →
← previous block·next block →recent activity