← previous blocknext block →recent activity
Analyzing
Block #91,780,265
30 transactions · 30 stateful · 2026-07-31 01:05:30 UTC
Parallelism
57/100
Blocked
67%
Avg conflicts / tx
2.13
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #91,780,265 · 30 txs across 13 waves · depth 13
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w47w08w19w210w511w613w719w523w626w1127w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xfb31d278…9107
0x34b655…2a6f
10 touches
10 conflicts
0x80656e3b…9240
0x34b655…2a6f
10 touches
10 conflicts
0xd039b252…bf63
0xd32edf…ff58
9 touches
10 conflicts
0x28c714d9…9438
0xa6afd3…d132
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x06e6ff87…e712
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
15 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity