← previous blocknext block →recent activity
Analyzing
Block #89,544,096
25 transactions · 25 stateful · 2026-07-23 02:02:44 UTC
Parallelism
72/100
Blocked
60%
Avg conflicts / tx
1.6
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #89,544,096 · 25 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w05w18w19w210w311w212w113w414w215w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0x9653bb2a…6cb3
0x34b655…2a6f
10 touches
10 conflicts
0x69d0a300…67ef
0x34b655…2a6f
8 touches
6 conflicts
0x6e19c9a0…7d86
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x42041fec…bd86
0x754704…b603
8 touches
6 conflicts
0x8d175439…fb79
0x34b655…2a6f
6 touches
3 conflicts
0xb476ee35…c627
0xa6afd3…d132
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
15 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity