← previous blocknext block →recent activity

Analyzing

Block #90,237,096

19 transactions · 16 stateful · 2026-07-25 15:24:09 UTC

Parallelism

68/100

Blocked

56%

Avg conflicts / tx

1.16

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #90,237,096  ·  19 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

0xe6e6f436…ddc0

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x2a56c465…4cc1

0xd32edf…ff58

7 touches
6 conflicts

0x00000000…00c9

0x34b655…2a6f

6 touches
3 conflicts

0x21aa9e7b…0a2d

0x34b655…2a6f

6 touches
3 conflicts

0x34a1ee7e…fb20

0x34b655…2a6f

6 touches
3 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0xbcbf5d09…8bac

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

10 conflicts on slot 0xe6e6f4364f…80ddc0

← previous block·next block →recent activity