← previous blocknext block →recent activity

Analyzing

Block #90,209,572

21 transactions · 21 stateful · 2026-07-25 13:05:23 UTC

Parallelism

71/100

Blocked

38%

Avg conflicts / tx

0.57

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #90,209,572  ·  21 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x5221f50f…0269

0x0a2fbf…29b1

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xf9e23360…8ef7

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0005

0x370e2e…63b4

6 touches
3 conflicts

0x9e2643cf…423d

0x370e2e…63b4

6 touches
3 conflicts

0x5221f50f…026a

0x0a2fbf…29b1

6 touches
3 conflicts

0x1bff683e…7ecb

0x754704…b603

6 touches
3 conflicts

0x00000000…0006

0x0a2fbf…29b1

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: 0x0a2fbf2d…f729b1

3 conflicts on slot 0x5221f50f69…460269

← previous block·next block →recent activity