← previous blocknext block →recent activity

Analyzing

Block #92,759,905

35 transactions · 30 stateful · 2026-08-03 11:13:55 UTC

Parallelism

71/100

Blocked

40%

Avg conflicts / tx

1.23

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #92,759,905  ·  35 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

0xbcbf5d09…8bac

0x34b655…2a6f

14 touches
21 conflicts

0xc824469a…6425

0x34b655…2a6f

12 touches
15 conflicts

0x4bb455b5…6ed7

0x34b655…2a6f

12 touches
15 conflicts

0xac2a0273…721b

0x34b655…2a6f

10 touches
10 conflicts

0x81561f70…fefd

0x34b655…2a6f

8 touches
6 conflicts

0x743061ce…a4ac

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…00c9

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

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

21 conflicts on slot 0xbcbf5d09a8…c68bac

← previous block·next block →recent activity