← previous blocknext block →recent activity
Analyzing
Block #91,097,231
42 transactions · 30 stateful · 2026-07-28 15:47:06 UTC
Parallelism
71/100
Blocked
67%
Avg conflicts / tx
1.71
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #91,097,231 · 42 txs across 12 waves · depth 12
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w26w39w010w120w021w122w223w324w425w527w628w729w832w433w334w936w439w1040w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0x07d8b1e8…78c6
0x34b655…2a6f
12 touches
15 conflicts
0xf4f9cac7…fd98
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x5250e2f6…9390
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x0a0cecef…4ed0
0x34b655…2a6f
8 touches
6 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
28 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity