← previous blocknext block →recent activity
Analyzing
Block #91,099,840
30 transactions · 29 stateful · 2026-07-28 16:00:14 UTC
Parallelism
40/100
Blocked
72%
Avg conflicts / tx
3.67
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #91,099,840 · 30 txs across 18 waves · depth 18
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w27w38w412w513w615w716w817w918w1019w1120w1221w1322w1423w1527w529w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
28 touches
91 conflicts
0x705ab4ae…0162
0x34b655…2a6f
22 touches
55 conflicts
0xbde524f4…43bf
0x34b655…2a6f
22 touches
55 conflicts
0x482471ad…122f
0x34b655…2a6f
22 touches
55 conflicts
0x36efe59d…0cf4
0x34b655…2a6f
15 touches
28 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x99701186…1cbf
0x34b655…2a6f
8 touches
6 conflicts
0xb39cb1d8…effa
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
91 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity