← previous blocknext block →recent activity
Analyzing
Block #89,580,029
14 transactions · 14 stateful · 2026-07-23 06:02:44 UTC
Parallelism
86/100
Blocked
14%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,580,029 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w07w08w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x64aaadbf…f9f3
0x34b655…2a6f
4 touches
1 conflict
0x5311f864…0984
0x754704…b603
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x63d46c0e…aa15
0x928dc8…8207
3 touches
1 conflict
0x63d46c0e…aa18
0x928dc8…8207
3 touches
1 conflict
0x63d46c0e…aa19
0x928dc8…8207
3 touches
1 conflict
0x7e5ea60a…c4aa
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 0x64aaadbf0a…79f9f3
Audit this contract →
← previous block·next block →recent activity