← previous blocknext block →recent activity
Analyzing
Block #91,973,022
17 transactions · 17 stateful · 2026-07-31 17:15:14 UTC
Parallelism
53/100
Blocked
53%
Avg conflicts / tx
1.06
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #91,973,022 · 17 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
1w02w13w24w35w37w48w59w611w114w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x841318e5…3005
0x34b655…2a6f
8 touches
6 conflicts
0xfe7e4874…18f5
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001a
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002a
0x1b6862…e19c
6 touches
3 conflicts
0x07b5c6c6…8865
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x31616f97…1acc
0x34b655…2a6f
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
6 conflicts on slot 0x841318e549…b13005
Audit this contract →
← previous block·next block →recent activity