← previous blocknext block →recent activity

Analyzing

Block #90,819,515

21 transactions · 19 stateful · 2026-07-27 16:29:03 UTC

Parallelism

71/100

Blocked

42%

Avg conflicts / tx

0.76

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #90,819,515  ·  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

0x0bd95eb4…e562

0x34b655…2a6f

6 touches
3 conflicts

0xd877e706…e9c0

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0x0fffa5c0…a3a9

0xa6afd3…d132

6 touches
3 conflicts

0x731f2745…9370

0xa6afd3…d132

6 touches
3 conflicts

0x4cabb80a…46bf

0x34b655…2a6f

6 touches
3 conflicts

0x90a021f0…f922

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

3 conflicts on slot 0x0bd95eb406…f6e562

← previous block·next block →recent activity