← previous blocknext block →recent activity
Analyzing
Block #89,853,899
13 transactions · 10 stateful · 2026-07-24 07:10:58 UTC
Parallelism
85/100
Blocked
10%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,853,899 · 13 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
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4886b3df…67a3
0x34b655…2a6f
4 touches
1 conflict
0x21e273cb…b384
0x34b655…2a6f
4 touches
1 conflict
0x024a7f41…8af8
0x34b655…2a6f
2 touches
0 conflicts
0x0b19c7e3…f181
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad04
0x34b655…2a6f
2 touches
0 conflicts
0x2697123c…8526
0x34b655…2a6f
2 touches
0 conflicts
0x42e8035e…485a
0x34b655…2a6f
2 touches
0 conflicts
0x4f51d069…d0b4
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 0x4886b3dfcf…0067a3
Audit this contract →
← previous block·next block →recent activity