← previous blocknext block →recent activity

Analyzing

Block #90,298,488

18 transactions · 18 stateful · 2026-07-25 20:34:38 UTC

Parallelism

72/100

Blocked

44%

Avg conflicts / tx

0.78

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #90,298,488  ·  18 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

0x96dd83e6…a507

0x34b655…2a6f

6 touches
3 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xf339290e…edd9

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x564e71cf…c7f7

0x34b655…2a6f

4 touches
1 conflict

0x5b56dd14…9884

0x34b655…2a6f

4 touches
1 conflict

0x74ed2a77…659b

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 0x96dd83e650…3fa507

← previous block·next block →recent activity