← previous blocknext block →recent activity
Analyzing
Block #89,560,575
22 transactions · 21 stateful · 2026-07-23 03:52:47 UTC
Parallelism
86/100
Blocked
29%
Avg conflicts / tx
0.45
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,560,575 · 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
1w03w04w15w18w011w012w015w116w219w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0363d65e…06d2
0x34b655…2a6f
6 touches
3 conflicts
0x861e5aef…d32c
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…002a
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xf8480e2a…dff0
0x1b6862…e19c
4 touches
1 conflict
0x2003d8cf…6836
0x34b655…2a6f
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 0x0363d65e7f…9306d2
Audit this contract →
← previous block·next block →recent activity