← previous blocknext block →recent activity
Analyzing
Block #91,424,617
70 transactions · 56 stateful · 2026-07-29 19:16:07 UTC
Parallelism
76/100
Blocked
75%
Avg conflicts / tx
3.63
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #91,424,617 · 70 txs across 17 waves · depth 17
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w011w012w115w217w319w120w121w222w423w324w425w229w433w336w537w638w739w840w942w1143w1246w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x48cba2…b48b
34 touches
136 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
20 touches
45 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
14 touches
21 conflicts
0x326a02b5…8dad
0x34b655…2a6f
12 touches
15 conflicts
0xc0eb79d1…29a4
0x34b655…2a6f
12 touches
15 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x2fd12b6c…02cc
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 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: 0x48cba278…e2b48b
136 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity