← previous blocknext block →recent activity
Analyzing
Block #91,444,252
40 transactions · 30 stateful · 2026-07-29 20:55:09 UTC
Parallelism
65/100
Blocked
67%
Avg conflicts / tx
1.75
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #91,444,252 · 40 txs across 14 waves · depth 14
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
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w17w014w015w116w217w318w421w522w623w224w325w726w329w730w831w936w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0xdd8e5705…17d6
0x34b655…2a6f
10 touches
10 conflicts
0xda2ee2e7…968a
0x34b655…2a6f
8 touches
6 conflicts
0x92115abd…ad76
0x34b655…2a6f
8 touches
6 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd6195af4…534d
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity