← previous blocknext block →recent activity
Analyzing
Block #91,409,748
52 transactions · 33 stateful · 2026-07-29 18:00:37 UTC
Parallelism
81/100
Blocked
64%
Avg conflicts / tx
1.1
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #91,409,748 · 52 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
5w07w19w011w112w216w319w420w022w126w227w333w034w135w236w338w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…0002
0x48cba2…b48b
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0xf7640726…19a2
0x2a68ba…90c5
8 touches
6 conflicts
0xcfe06a18…b5b5
0x2b46c0…1669
6 touches
3 conflicts
0xd8fd2add…50fc
0x2b46c0…1669
6 touches
3 conflicts
0x482471ad…122f
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
15 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity