← previous blocknext block →recent activity

Analyzing

Block #90,274,231

27 transactions · 24 stateful · 2026-07-25 18:31:20 UTC

Parallelism

67/100

Blocked

38%

Avg conflicts / tx

1.37

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #90,274,231  ·  27 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

16 touches
28 conflicts

0x6923e5e6…3053

0x34b655…2a6f

16 touches
28 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

16 touches
28 conflicts

0x482471ad…122f

0x34b655…2a6f

14 touches
21 conflicts

0x4bfdcd51…9b58

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6426

0x34b655…2a6f

8 touches
6 conflicts

0x231ccc13…a7c6

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…00c9

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

28 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity