← previous blocknext block →recent activity
Analyzing
Block #89,681,121
22 transactions · 21 stateful · 2026-07-23 16:39:03 UTC
Parallelism
73/100
Blocked
43%
Avg conflicts / tx
0.73
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #89,681,121 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w09w110w212w315w216w417w520w221w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xabfb6289…f23b
0x34b655…2a6f
8 touches
6 conflicts
0x7a2c83a3…a29a
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x861e5aef…d32c
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x98212952…9ba6
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 0xabfb628974…6df23b
Audit this contract →
← previous block·next block →recent activity