← previous blocknext block →recent activity

Analyzing

Block #92,372,335

19 transactions · 19 stateful · 2026-08-02 02:43:31 UTC

Parallelism

53/100

Blocked

53%

Avg conflicts / tx

1.42

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #92,372,335  ·  19 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

10 touches
10 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

10 touches
10 conflicts

0x2e1f5171…ad2d

0x34b655…2a6f

10 touches
10 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0x326a02b5…8dad

0x34b655…2a6f

8 touches
6 conflicts

0xbd96f96f…5843

0x34b655…2a6f

8 touches
6 conflicts

0x42522e76…2592

0x34b655…2a6f

8 touches
6 conflicts

0x77c4bb4a…4ad3

0x34b655…2a6f

7 touches
6 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

10 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity