← previous blocknext block →recent activity
Analyzing
Block #91,104,219
22 transactions · 21 stateful · 2026-07-28 16:22:15 UTC
Parallelism
55/100
Blocked
52%
Avg conflicts / tx
2.09
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #91,104,219 · 22 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
1w02w13w04w07w111w112w213w314w415w516w617w718w819w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
18 touches
36 conflicts
0x705ab4ae…0162
0x34b655…2a6f
16 touches
28 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0x0e1dab48…e4b7
0x34b655…2a6f
7 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x9af9ce68…9702
0x34b655…2a6f
6 touches
3 conflicts
0x85562217…0ca2
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
36 conflicts on slot 0xbde524f475…b143bf
Audit this contract →
← previous block·next block →recent activity