← previous blocknext block →recent activity

Analyzing

Block #90,802,074

18 transactions · 18 stateful · 2026-07-27 15:01:14 UTC

Parallelism

61/100

Blocked

61%

Avg conflicts / tx

1.56

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #90,802,074  ·  18 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

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x310afe2c…83e1

0x34b655…2a6f

8 touches
6 conflicts

0x9ba6ae4a…90cb

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…00c9

0x34b655…2a6f

6 touches
3 conflicts

0x20a8fb67…1310

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0x8743e1ba…8331

0x34b655…2a6f

6 touches
3 conflicts

0xabd0bcfc…64e2

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

6 conflicts on slot 0x310afe2cd5…d683e1

← previous block·next block →recent activity