← previous blocknext block →recent activity

Analyzing

Block #92,757,458

31 transactions · 31 stateful · 2026-08-03 11:01:37 UTC

Parallelism

68/100

Blocked

32%

Avg conflicts / tx

1.55

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #92,757,458  ·  31 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0xc824469a…6425

0x34b655…2a6f

18 touches
36 conflicts

0x482471ad…122f

0x34b655…2a6f

18 touches
36 conflicts

0xca2926e0…61b5

0x34b655…2a6f

16 touches
28 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

10 touches
10 conflicts

0xc9e26446…95f7

0x34b655…2a6f

8 touches
6 conflicts

0x94aff148…b584

0x34b655…2a6f

6 touches
3 conflicts

0xc3baa205…f26e

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…641f

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

36 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity