← previous blocknext block →recent activity
Analyzing
Block #89,416,481
21 transactions · 19 stateful · 2026-07-22 11:50:11 UTC
Parallelism
71/100
Blocked
42%
Avg conflicts / tx
0.81
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #89,416,481 · 21 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
3w04w06w18w112w216w117w218w319w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x64aaadbf…f9f3
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x3ec02283…6846
0x34b655…2a6f
6 touches
3 conflicts
0x3d789f42…57d6
0x34b655…2a6f
6 touches
3 conflicts
0x7f6581c2…7ade
0x34b655…2a6f
6 touches
3 conflicts
0x88f37d98…6792
0x34b655…2a6f
6 touches
3 conflicts
0x322dcd34…8718
0x34b655…2a6f
4 touches
1 conflict
0x36890fff…f3d1
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
10 conflicts on slot 0x64aaadbf0a…79f9f3
Audit this contract →
← previous block·next block →recent activity