← previous blocknext block →recent activity
Analyzing
Block #89,412,762
18 transactions · 18 stateful · 2026-07-22 11:25:21 UTC
Parallelism
78/100
Blocked
33%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,412,762 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w07w08w19w111w012w113w215w317w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1941b441…5889
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x405da62e…192a
0xa6afd3…d132
4 touches
1 conflict
0x066e1e8a…d0f8
0x065c9d…c394
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0xcbe18c62…3a5c
0x34b655…2a6f
4 touches
1 conflict
0xcbe18c62…3a5d
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
3 conflicts on slot 0x1941b4413e…0c5889
Audit this contract →
← previous block·next block →recent activity