← previous blocknext block →recent activity
Analyzing
Block #91,099,592
18 transactions · 18 stateful · 2026-07-28 15:58:59 UTC
Parallelism
44/100
Blocked
56%
Avg conflicts / tx
2.39
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #91,099,592 · 18 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
1w02w13w26w37w48w59w610w711w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
18 touches
36 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
18 touches
36 conflicts
0xbde524f4…43bf
0x34b655…2a6f
14 touches
21 conflicts
0x705ab4ae…0162
0x34b655…2a6f
12 touches
15 conflicts
0x247c9993…833d
0x34b655…2a6f
9 touches
10 conflicts
0xad4f517c…0dce
0x34b655…2a6f
5 touches
3 conflicts
0xa68dfacc…cdb8
0x34b655…2a6f
4 touches
1 conflict
0xabec3222…dec0
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
36 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity