← previous blocknext block →recent activity
Analyzing
Block #90,534,909
24 transactions · 22 stateful · 2026-07-26 16:37:11 UTC
Parallelism
71/100
Blocked
59%
Avg conflicts / tx
1.17
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #90,534,909 · 24 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w06w17w28w39w412w313w414w515w117w618w222w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1e56f6b6…5940
0x34b655…2a6f
10 touches
10 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x3de501bc…51f1
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0x48cba2…b48b
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x103be197…826c
0xa6afd3…d132
6 touches
3 conflicts
0x66a11a3b…0ee9
0xa6afd3…d132
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
10 conflicts on slot 0x1e56f6b6e1…615940
Audit this contract →
← previous block·next block →recent activity