← previous blocknext block →recent activity
Analyzing
Block #89,703,001
12 transactions · 11 stateful · 2026-07-23 18:29:22 UTC
Parallelism
83/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,703,001 · 12 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
0x013a6b08…d120
0x34b655…2a6f
4 touches
1 conflict
0x7b6c252d…a696
0x34b655…2a6f
4 touches
1 conflict
0xafc8de01…40dc
0x34b655…2a6f
4 touches
1 conflict
0xb4f4fd9a…2679
0x34b655…2a6f
4 touches
1 conflict
0x06655163…4efc
0x065c9d…c394
2 touches
0 conflicts
0x244bd9cd…ebc1
0x065c9d…c394
2 touches
0 conflicts
0x28c47824…6fd6
0x065c9d…c394
2 touches
0 conflicts
0xa17b9bf3…3cd0
0x065c9d…c394
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 0x013a6b0813…a1d120
Audit this contract →
← previous block·next block →recent activity