← previous blocknext block →recent activity
Analyzing
Block #89,770,257
10 transactions · 9 stateful · 2026-07-24 00:08:59 UTC
Parallelism
70/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,770,257 · 10 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
3w05w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa3401b0e…8681
0x34b655…2a6f
4 touches
1 conflict
0x86c98782…f3b7
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x68ec2abe…cbe6
0x065c9d…c394
2 touches
0 conflicts
0x9034a751…226d
0x065c9d…c394
2 touches
0 conflicts
0xf12b92e8…6c9e
0x065c9d…c394
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x06e40499…165e
0x2b46c0…1669
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 0xa3401b0e38…cf8681
Audit this contract →
← previous block·next block →recent activity