← previous blocknext block →recent activity
Analyzing
Block #89,703,260
22 transactions · 15 stateful · 2026-07-23 18:30:40 UTC
Parallelism
86/100
Blocked
20%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,703,260 · 22 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
1w06w07w09w111w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xacca1d4f…d6df
0x34b655…2a6f
4 touches
1 conflict
0xba853d70…0f57
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xe822ddee…ca34
0x34b655…2a6f
4 touches
1 conflict
0xe822ddee…ca35
0x34b655…2a6f
4 touches
1 conflict
0x1e56f6b6…5940
0x34b655…2a6f
4 touches
1 conflict
0x41bd2e6b…e240
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
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: Perpl
1 conflict on slot 0xacca1d4f20…d4d6df
Audit this contract →
← previous block·next block →recent activity