← previous blocknext block →recent activity
Analyzing
Block #91,405,358
32 transactions · 23 stateful · 2026-07-29 17:38:20 UTC
Parallelism
78/100
Blocked
39%
Avg conflicts / tx
0.69
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #91,405,358 · 32 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w112w013w114w217w218w324w426w527w628w029w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0ab54c30…b88e
0x34b655…2a6f
10 touches
10 conflicts
0x7be3246e…f89f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe48750bb…a4dd
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
10 conflicts on slot 0x0ab54c30a6…82b88e
Audit this contract →
← previous block·next block →recent activity