← previous blocknext block →recent activity

Analyzing

Block #94,681,256

17 transactions · 16 stateful · 2026-08-10 04:34:15 UTC

Parallelism

76/100

Blocked

56%

Avg conflicts / tx

1

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #94,681,256  ·  17 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

8 touches
6 conflicts

0x00000000…003d

0xa6afd3…d132

8 touches
6 conflicts

0x66a11a3b…0ee9

0xa6afd3…d132

8 touches
6 conflicts

0x737acb78…fce8

0x34b655…2a6f

6 touches
3 conflicts

0x103be197…826c

0xa6afd3…d132

6 touches
3 conflicts

0x5502e1cc…3910

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…00c9

0x34b655…2a6f

4 touches
1 conflict

0x34defd62…0513

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

6 conflicts on slot 0xac2a02739b…81721b

← previous block·next block →recent activity