← previous blocknext block →recent activity
Analyzing
Block #89,386,914
34 transactions · 28 stateful · 2026-07-22 08:32:30 UTC
Parallelism
79/100
Blocked
57%
Avg conflicts / tx
0.97
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #89,386,914 · 34 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
1w02w13w29w310w411w413w316w417w518w620w021w122w223w324w428w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x47bef643…2dfe
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0002
0x48cba2…b48b
8 touches
6 conflicts
0x00000000…001e
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0xba5743c7…21c5
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002e
0x1b6862…e19c
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity