← previous blocknext block →recent activity

Analyzing

Block #92,759,498

19 transactions · 19 stateful · 2026-08-03 11:11:52 UTC

Parallelism

84/100

Blocked

32%

Avg conflicts / tx

0.47

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #92,759,498  ·  19 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x81561f70…fefd

0x34b655…2a6f

6 touches
3 conflicts

0x1280f157…ac8e

0x34b655…2a6f

6 touches
3 conflicts

0xbde524f4…43bf

0x34b655…2a6f

6 touches
3 conflicts

0xce06a0f7…efef

0x34b655…2a6f

6 touches
3 conflicts

0xb9488e5f…c6da

0x34b655…2a6f

5 touches
3 conflicts

0xeab6e128…e39e

0x34b655…2a6f

4 touches
1 conflict

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

3 conflicts on slot 0xac2a02739b…81721b

← previous block·next block →recent activity