← previous blocknext block →recent activity

Analyzing

Block #90,914,819

18 transactions · 17 stateful · 2026-07-28 00:28:32 UTC

Parallelism

78/100

Blocked

41%

Avg conflicts / tx

0.78

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #90,914,819  ·  18 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x8cd684d0…c3cb

0x34b655…2a6f

8 touches
6 conflicts

0x5229d4af…173b

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0x66b3ebbe…d253

0x34b655…2a6f

4 touches
1 conflict

0x948836ff…59ab

0x34b655…2a6f

4 touches
1 conflict

0x966e45cf…0f25

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 0x8cd684d0d7…f5c3cb

← previous block·next block →recent activity