← previous blocknext block →recent activity

Analyzing

Block #93,345,866

19 transactions · 19 stateful · 2026-08-05 12:22:40 UTC

Parallelism

58/100

Blocked

53%

Avg conflicts / tx

1.32

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #93,345,866  ·  19 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xa3a621f8…75a2

0x34b655…2a6f

8 touches
6 conflicts

0xdba08802…6ba7

0x34b655…2a6f

8 touches
6 conflicts

0x41f1e2e5…2edf

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0xb6ed511f…6b68

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xf5ea108a…dbf6

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

6 conflicts on slot 0xa3a621f8f3…6975a2

← previous block·next block →recent activity