← previous blocknext block →recent activity

Analyzing

Block #90,817,511

18 transactions · 17 stateful · 2026-07-27 16:18:58 UTC

Parallelism

56/100

Blocked

59%

Avg conflicts / tx

1.11

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #90,817,511  ·  18 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x6fe7d366…78ff

0x34b655…2a6f

10 touches
10 conflicts

0x5484fc7f…a8d8

0x34b655…2a6f

6 touches
3 conflicts

0xb476ee35…c627

0xa6afd3…d132

6 touches
3 conflicts

0x28c714d9…9438

0xa6afd3…d132

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x0bd95eb4…e562

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

10 conflicts on slot 0x6fe7d366be…a578ff

← previous block·next block →recent activity