← previous blocknext block →recent activity

Analyzing

Block #94,717,031

25 transactions · 21 stateful · 2026-08-10 07:34:11 UTC

Parallelism

80/100

Blocked

38%

Avg conflicts / tx

0.6

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #94,717,031  ·  25 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

0xbca10637…e8ad

0x34b655…2a6f

8 touches
6 conflicts

0xea0a07a8…c851

0xd32edf…ff58

7 touches
6 conflicts

0x217bd767…b79e

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x94b9344b…f7eb

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…00c9

0x34b655…2a6f

6 touches
3 conflicts

0x897a7a69…3d3e

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…641f

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 0xbca10637e3…94e8ad

← previous block·next block →recent activity