← previous blocknext block →recent activity

Analyzing

Block #92,869,070

26 transactions · 24 stateful · 2026-08-03 20:23:20 UTC

Parallelism

65/100

Blocked

46%

Avg conflicts / tx

1.46

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #92,869,070  ·  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

0xc824469a…6425

0x34b655…2a6f

16 touches
28 conflicts

0xc2b861af…5ad5

0x34b655…2a6f

14 touches
21 conflicts

0x482471ad…122f

0x34b655…2a6f

14 touches
21 conflicts

0x948836ff…59ab

0x34b655…2a6f

6 touches
3 conflicts

0x38bdc5d3…a632

0x34b655…2a6f

6 touches
3 conflicts

0xd66696e0…0842

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0x6ff9c682…345d

0x34b655…2a6f

4 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

28 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity