← previous blocknext block →recent activity
Analyzing
Block #89,571,246
8 transactions · 7 stateful · 2026-07-23 05:04:10 UTC
Parallelism
63/100
Blocked
29%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,571,246 · 8 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
1w04w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x2b8d9898…d525
0x34b655…2a6f
4 touches
1 conflict
0x82dd2252…e1ce
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x06df379f…2653
0x34b655…2a6f
2 touches
0 conflicts
0x18e37e7d…bab2
0x34b655…2a6f
2 touches
0 conflicts
0x19e99d1b…e06c
0x34b655…2a6f
2 touches
0 conflicts
0x318ea3ca…a6ff
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 0x326a02b5c5…5c8dad
Audit this contract →
← previous block·next block →recent activity