← previous blocknext block →recent activity
Analyzing
Block #91,099,063
41 transactions · 30 stateful · 2026-07-28 15:56:19 UTC
Parallelism
76/100
Blocked
60%
Avg conflicts / tx
1.44
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #91,099,063 · 41 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
2w04w05w16w27w39w111w019w020w121w222w323w426w428w429w530w531w632w634w637w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0x103be197…826c
0xa6afd3…d132
10 touches
10 conflicts
0x439cfb2c…7b9e
0xa6afd3…d132
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x1bf8d2af…d140
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0xb9834665…e363
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
10 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity