← previous blocknext block →recent activity
Analyzing
Block #89,881,168
15 transactions · 14 stateful · 2026-07-24 09:28:08 UTC
Parallelism
60/100
Blocked
50%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #89,881,168 · 15 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
1w02w13w04w16w27w08w110w313w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x2078c8e9…8a21
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x7781d5f0…4940
0x34b655…2a6f
6 touches
3 conflicts
0xbc65c4f6…9da7
0x34b655…2a6f
6 touches
3 conflicts
0xa4dc1328…d42d
0x34b655…2a6f
6 touches
3 conflicts
0xb9b4eff6…c3ef
0x34b655…2a6f
6 touches
3 conflicts
0xe57232b3…0fbf
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity