← previous blocknext block →recent activity
Analyzing
Block #89,539,268
14 transactions · 14 stateful · 2026-07-23 01:30:27 UTC
Parallelism
86/100
Blocked
21%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,539,268 · 14 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
1w05w07w09w110w112w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1e10796e…6213
0x34b655…2a6f
4 touches
1 conflict
0x1e10796e…6214
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xb13b96bd…a3cb
0x34b655…2a6f
4 touches
1 conflict
0x046740ca…4065
0x34b655…2a6f
2 touches
0 conflicts
0x046740ca…4066
0x34b655…2a6f
2 touches
0 conflicts
0x01a89030…f786
0x368ee5…7ca4
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 0x1e10796e66…086213
Audit this contract →
← previous block·next block →recent activity