← previous blocknext block →recent activity
Analyzing
Block #91,768,312
29 transactions · 27 stateful · 2026-07-31 00:05:22 UTC
Parallelism
66/100
Blocked
44%
Avg conflicts / tx
1.41
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #91,768,312 · 29 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w210w011w312w414w515w619w120w721w526w827w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x99c5409a…25b7
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0x9fab1a24…397f
0x34b655…2a6f
12 touches
15 conflicts
0x5fe7e126…6dd2
0x34b655…2a6f
8 touches
6 conflicts
0x4848cef8…a1cb
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0x8218911e…3bed
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
21 conflicts on slot 0x99c5409a28…0025b7
Audit this contract →
← previous block·next block →recent activity