← previous blocknext block →recent activity
Analyzing
Block #89,403,746
18 transactions · 17 stateful · 2026-07-22 10:25:04 UTC
Parallelism
56/100
Blocked
53%
Avg conflicts / tx
1.33
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #89,403,746 · 18 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w48w314w415w516w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5c16527f…628c
0x34b655…2a6f
10 touches
10 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x41377979…0a18
0x34b655…2a6f
8 touches
6 conflicts
0x63f1572a…74e2
0x34b655…2a6f
6 touches
3 conflicts
0x70de1ba5…6ebb
0x34b655…2a6f
6 touches
3 conflicts
0xce0dd398…6988
0x34b655…2a6f
6 touches
3 conflicts
0xb01c7dc7…f105
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 0x5c16527f85…5b628c
Audit this contract →
← previous block·next block →recent activity