← previous blocknext block →recent activity

Analyzing

Block #95,154,511

21 transactions · 21 stateful · 2026-08-11 20:17:01 UTC

Parallelism

67/100

Blocked

67%

Avg conflicts / tx

1.71

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #95,154,511  ·  21 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x27dd8ebd…6d57

0x34b655…2a6f

10 touches
10 conflicts

0xf5ea108a…dbf6

0x34b655…2a6f

10 touches
10 conflicts

0x737acb78…fce8

0x34b655…2a6f

8 touches
6 conflicts

0x424934c8…f2f1

0x34b655…2a6f

8 touches
6 conflicts

0xac2a0273…721b

0x34b655…2a6f

8 touches
6 conflicts

0x734ee320…caae

0x34b655…2a6f

6 touches
3 conflicts

0xbfb4b02a…4b47

0x34b655…2a6f

6 touches
3 conflicts

0xa9af0099…3165

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

10 conflicts on slot 0x27dd8ebdeb…c76d57

← previous block·next block →recent activity