← previous blocknext block →recent activity
Analyzing
Block #91,764,838
17 transactions · 15 stateful · 2026-07-30 23:47:53 UTC
Parallelism
76/100
Blocked
47%
Avg conflicts / tx
0.59
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,764,838 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w06w19w010w112w113w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x26444b91…765e
0x34b655…2a6f
6 touches
3 conflicts
0xc751242c…efac
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xf3994e7e…6290
0x34b655…2a6f
6 touches
3 conflicts
0xb8213a0f…13ec
0xd32edf…ff58
5 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x3eede796…d745
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
3 conflicts on slot 0x26444b91f3…d7765e
Audit this contract →
← previous block·next block →recent activity