← previous blocknext block →recent activity

Analyzing

Block #95,114,956

25 transactions · 22 stateful · 2026-08-11 16:58:03 UTC

Parallelism

68/100

Blocked

59%

Avg conflicts / tx

1.76

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #95,114,956  ·  25 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

0x745952b2…d90c

0x34b655…2a6f

12 touches
15 conflicts

0xac2a0273…721b

0x34b655…2a6f

10 touches
10 conflicts

0x737acb78…fce8

0x34b655…2a6f

10 touches
10 conflicts

0xa56e54d0…2d39

0x34b655…2a6f

8 touches
6 conflicts

0xbde524f4…43bf

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xc0eb79d1…29a4

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

15 conflicts on slot 0x745952b2a0…a6d90c

← previous block·next block →recent activity