← previous blocknext block →recent activity
Analyzing
Block #90,791,558
34 transactions · 33 stateful · 2026-07-27 14:08:19 UTC
Parallelism
76/100
Blocked
73%
Avg conflicts / tx
2.09
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #90,791,558 · 34 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w26w37w08w19w210w311w412w013w114w215w316w418w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x033cf007…136d
0x34b655…2a6f
14 touches
21 conflicts
0xbde524f4…43bf
0x34b655…2a6f
12 touches
15 conflicts
0x4bc1abab…5874
0x34b655…2a6f
12 touches
15 conflicts
0xea02471d…1542
0x34b655…2a6f
12 touches
15 conflicts
0xf3d10975…0d07
0x34b655…2a6f
12 touches
15 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0002
0x48cba2…b48b
10 touches
10 conflicts
0xb2022d4d…0ca0
0xa6afd3…d132
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
21 conflicts on slot 0x033cf007c8…d2136d
Audit this contract →
← previous block·next block →recent activity