← previous blocknext block →recent activity

Analyzing

Block #92,752,788

24 transactions · 20 stateful · 2026-08-03 10:38:07 UTC

Parallelism

79/100

Blocked

40%

Avg conflicts / tx

0.71

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #92,752,788  ·  24 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x04ab5947…620f

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6426

0x34b655…2a6f

6 touches
3 conflicts

0xca2926e0…61b5

0x34b655…2a6f

6 touches
3 conflicts

0xd66696e0…0842

0x34b655…2a6f

6 touches
3 conflicts

0x3359e4ab…1ef4

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x889d5e90…929a

0x2a68ba…90c5

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

6 conflicts on slot 0x04ab594719…29620f

← previous block·next block →recent activity