← previous blocknext block →recent activity
Analyzing
Block #91,103,782
29 transactions · 27 stateful · 2026-07-28 16:20:04 UTC
Parallelism
45/100
Blocked
67%
Avg conflicts / tx
3.17
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #91,103,782 · 29 txs across 16 waves · depth 16
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w17w08w19w210w311w312w213w415w517w618w719w820w921w1022w1123w1224w1325w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
26 touches
78 conflicts
0xc824469a…6425
0x34b655…2a6f
26 touches
78 conflicts
0xbde524f4…43bf
0x34b655…2a6f
20 touches
45 conflicts
0x705ab4ae…0162
0x34b655…2a6f
20 touches
45 conflicts
0x10cd16f5…ccbf
0x34b655…2a6f
9 touches
10 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xa04ff67a…6fbe
0x34b655…2a6f
8 touches
6 conflicts
0xb39cb1d8…effa
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
78 conflicts on slot 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity