← previous blocknext block →recent activity
Analyzing
Block #89,694,211
11 transactions · 10 stateful · 2026-07-23 17:45:06 UTC
Parallelism
64/100
Blocked
30%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,694,211 · 11 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
1w02w13w09w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc92ea287…c4df
0x34b655…2a6f
4 touches
1 conflict
0x0f2d78b1…7363
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x12978194…d32f
0x34b655…2a6f
2 touches
0 conflicts
0x34cd673f…ef42
0x34b655…2a6f
2 touches
0 conflicts
0x51028c5e…235c
0x34b655…2a6f
2 touches
0 conflicts
0x6bdd6387…7ffa
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 0xc92ea287fd…ddc4df
Audit this contract →
← previous block·next block →recent activity