← previous blocknext block →recent activity
Analyzing
Block #89,676,887
21 transactions · 14 stateful · 2026-07-23 16:17:40 UTC
Parallelism
81/100
Blocked
43%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,676,887 · 21 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
4w05w19w010w111w212w314w016w119w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xc948dbdc…199a
0x34b655…2a6f
6 touches
3 conflicts
0x1a3d2527…8ca0
0x34b655…2a6f
4 touches
1 conflict
0x8a705be8…7ac4
0xc8689a…ee79
4 touches
1 conflict
0x183c10a3…2e0a
0x34b655…2a6f
4 touches
1 conflict
0x546c7039…83ac
0x34b655…2a6f
4 touches
1 conflict
0x6fc11396…2d22
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
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
6 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity