← previous blocknext block →recent activity

Analyzing

Block #90,960,516

22 transactions · 20 stateful · 2026-07-28 04:18:22 UTC

Parallelism

55/100

Blocked

55%

Avg conflicts / tx

1.27

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #90,960,516  ·  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

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0xc824469a…6425

0x34b655…2a6f

14 touches
21 conflicts

0x705ab4ae…0162

0x34b655…2a6f

12 touches
15 conflicts

0xbde524f4…43bf

0x34b655…2a6f

12 touches
15 conflicts

0x482471ad…122f

0x34b655…2a6f

12 touches
15 conflicts

0x7c0a113b…de60

0x34b655…2a6f

6 touches
3 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0x3a62b0ca…9292

0x34b655…2a6f

5 touches
3 conflicts

0xfddb964d…5934

0x34b655…2a6f

4 touches
1 conflict

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 0xc824469a90…af6425

← previous block·next block →recent activity