← previous blocknext block →recent activity

Analyzing

Block #95,539,566

24 transactions · 21 stateful · 2026-08-13 04:47:21 UTC

Parallelism

79/100

Blocked

33%

Avg conflicts / tx

0.42

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #95,539,566  ·  24 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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x40c49f…2af0

6 touches
3 conflicts

0x342fbbca…d443

0x40c49f…2af0

6 touches
3 conflicts

0xffa7d0a4…b10a

0x40c49f…2af0

6 touches
3 conflicts

0x25b748bd…2e56

0x34b655…2a6f

4 touches
1 conflict

0x42e917f7…ed8c

0x34b655…2a6f

4 touches
1 conflict

0x43fd3667…094b

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

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

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity