← previous blocknext block →recent activity

Analyzing

Block #92,531,848

18 transactions · 18 stateful · 2026-08-02 16:05:45 UTC

Parallelism

56/100

Blocked

50%

Avg conflicts / tx

1.06

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #92,531,848  ·  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

0xff196840…a453

0x34b655…2a6f

8 touches
6 conflicts

0x4e87f089…906c

0xd32edf…ff58

7 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…001d

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…002d

0x1b6862…e19c

6 touches
3 conflicts

0xba5743c7…21c4

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x1fd19887…8e0e

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

6 conflicts on slot 0xff19684070…f2a453

← previous block·next block →recent activity