← previous blocknext block →recent activity

Analyzing

Block #90,893,969

25 transactions · 22 stateful · 2026-07-27 22:43:37 UTC

Parallelism

80/100

Blocked

27%

Avg conflicts / tx

0.48

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #90,893,969  ·  25 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0xa9660e2b…64df

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0xcdc1731c…b91a

0x34b655…2a6f

4 touches
1 conflict

0xe6e6f436…ddc0

0x34b655…2a6f

4 touches
1 conflict

0xeff94efd…f7d7

0x34b655…2a6f

4 touches
1 conflict

0xfcea0c54…587f

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

6 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity