← previous blocknext block →recent activity
Analyzing
Block #89,870,605
11 transactions · 9 stateful · 2026-07-24 08:35:00 UTC
Parallelism
82/100
Blocked
22%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,870,605 · 11 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
5w06w07w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa37f6251…f3c1
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xfefd9ff3…81b2
0x34b655…2a6f
4 touches
1 conflict
0xb415dca6…5bdd
0x34b655…2a6f
4 touches
1 conflict
0x6dcb5d8d…5f07
0x34b655…2a6f
4 touches
1 conflict
0xb415dca6…5bdc
0x34b655…2a6f
4 touches
1 conflict
0xc064fe79…319f
0x34b655…2a6f
3 touches
1 conflict
0xac2a0273…7212
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 0xa37f62515d…ddf3c1
Audit this contract →
← previous block·next block →recent activity