← previous blocknext block →recent activity
Analyzing
Block #89,873,699
10 transactions · 10 stateful · 2026-07-24 08:50:34 UTC
Parallelism
80/100
Blocked
10%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,873,699 · 10 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
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xffc8b799…3587
0x34b655…2a6f
4 touches
1 conflict
0x83f3d320…fb59
0x34b655…2a6f
4 touches
1 conflict
0x42d5e8f3…5930
0x34b655…2a6f
4 touches
1 conflict
0x52657682…1ae4
0x34b655…2a6f
3 touches
1 conflict
0x08fc6a3c…b5d9
0x065c9d…c394
2 touches
0 conflicts
0x6290c525…20d9
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 0xffc8b79980…e73587
Audit this contract →
← previous block·next block →recent activity