← previous blocknext block →recent activity
Analyzing
Block #89,676,149
15 transactions · 14 stateful · 2026-07-23 16:13:53 UTC
Parallelism
60/100
Blocked
64%
Avg conflicts / tx
1.73
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #89,676,149 · 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
1w03w04w16w27w18w310w111w212w313w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x326a02b5…8dad
0x34b655…2a6f
8 touches
6 conflicts
0x02d895f0…2b93
0x34b655…2a6f
6 touches
3 conflicts
0x120847e2…98c2
0x34b655…2a6f
6 touches
3 conflicts
0x34d4ef1a…0345
0x34b655…2a6f
6 touches
3 conflicts
0x393a6e65…e8a2
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
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
10 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity