← previous blocknext block →recent activity
Analyzing
Block #89,857,256
11 transactions · 11 stateful · 2026-07-24 07:27:51 UTC
Parallelism
64/100
Blocked
45%
Avg conflicts / tx
0.91
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,857,256 · 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
1w02w13w04w25w38w09w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8b87ece6…3353
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x1321736a…43e3
0x34b655…2a6f
4 touches
1 conflict
0x1bca2e98…f0ca
0x34b655…2a6f
4 touches
1 conflict
0x34a2c248…f7ed
0x34b655…2a6f
4 touches
1 conflict
0x3de86e79…4d3d
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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 0x8b87ece64f…f33353
Audit this contract →
← previous block·next block →recent activity