← previous blocknext block →recent activity
Analyzing
Block #89,741,664
21 transactions · 20 stateful · 2026-07-23 21:44:36 UTC
Parallelism
86/100
Blocked
45%
Avg conflicts / tx
0.52
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,741,664 · 21 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
4w05w16w07w19w110w012w013w114w215w216w117w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0b0c2e8d…c1b8
0xe52b14…7230
6 touches
3 conflicts
0xf79df061…e005
0xe52b14…7230
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x2c2db8e9…fdc7
0x34b655…2a6f
4 touches
1 conflict
0x4f394483…ff62
0x34b655…2a6f
4 touches
1 conflict
0x59dccbd8…2bf6
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
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: 0xe52b1424…bb7230
3 conflicts on slot 0x0b0c2e8d5e…dbc1b8
Audit this contract →
← previous block·next block →recent activity