← previous blocknext block →recent activity

Analyzing

Block #92,222,464

26 transactions · 24 stateful · 2026-08-01 14:09:45 UTC

Parallelism

65/100

Blocked

46%

Avg conflicts / tx

1.08

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #92,222,464  ·  26 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

0xca841faa…486a

0x34b655…2a6f

12 touches
15 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

8 touches
6 conflicts

0x326a02b5…8dad

0x34b655…2a6f

6 touches
3 conflicts

0xa457c06e…2f06

0x34b655…2a6f

6 touches
3 conflicts

0xa53250c9…f399

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xf007a4f4…507d

0x34b655…2a6f

6 touches
3 conflicts

0x083ff337…401b

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

15 conflicts on slot 0xca841faae5…71486a

← previous block·next block →recent activity