← previous blocknext block →recent activity
Analyzing
Block #91,435,211
65 transactions · 44 stateful · 2026-07-29 20:09:40 UTC
Parallelism
71/100
Blocked
68%
Avg conflicts / tx
2.28
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #91,435,211 · 65 txs across 19 waves · depth 19
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
wave w14
wave w15
wave w16
wave w17
wave w18
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w25w313w014w016w017w119w022w125w226w433w034w135w236w337w438w549w351w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
24 touches
66 conflicts
0x17606ba6…1b6e
0x754704…b603
10 touches
10 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0x033cf007…136d
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…00c9
0x34b655…2a6f
10 touches
10 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0xf3d10975…0d07
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
66 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity