← previous blocknext block →recent activity

Analyzing

Block #95,350,338

25 transactions · 21 stateful · 2026-08-12 12:53:08 UTC

Parallelism

84/100

Blocked

33%

Avg conflicts / tx

0.4

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #95,350,338  ·  25 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

0xbde524f4…43bf

0x34b655…2a6f

8 touches
6 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x737acb78…fce8

0x34b655…2a6f

6 touches
3 conflicts

0x8c19ca66…7807

0x34b655…2a6f

6 touches
3 conflicts

0xac15405f…4ac4

0x34b655…2a6f

5 touches
3 conflicts

0xce06a0f7…efef

0x34b655…2a6f

5 touches
3 conflicts

0x78cb41e1…f2c1

0xfa32f9…f3f0

4 touches
1 conflict

0x72b220d0…c85d

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 0xbde524f475…b143bf

← previous block·next block →recent activity