← previous blocknext block →recent activity
Analyzing
Block #91,235,794
19 transactions · 18 stateful · 2026-07-29 03:24:07 UTC
Parallelism
68/100
Blocked
39%
Avg conflicts / tx
0.74
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,235,794 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w06w17w29w010w311w412w413w517w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…00c9
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad06
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad07
0x34b655…2a6f
8 touches
6 conflicts
0x53d66dce…b6a3
0x34b655…2a6f
8 touches
6 conflicts
0x8727ada9…770d
0x34b655…2a6f
8 touches
6 conflicts
0xa457c06e…2f06
0x34b655…2a6f
8 touches
6 conflicts
0xebbd51a8…2e65
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
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
6 conflicts on slot 0x0000000000…0000c9
Audit this contract →
← previous block·next block →recent activity