← previous blocknext block →recent activity

Analyzing

Block #95,797,384

22 transactions · 17 stateful · 2026-08-14 02:25:08 UTC

Parallelism

73/100

Blocked

53%

Avg conflicts / tx

1.23

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #95,797,384  ·  22 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x4c619b7d…f4fa

0x34b655…2a6f

10 touches
10 conflicts

0x4efae872…6aa8

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0x482471ad…122f

0x34b655…2a6f

10 touches
10 conflicts

0xca841faa…486a

0x34b655…2a6f

8 touches
6 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0x948836ff…59ab

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

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

10 conflicts on slot 0x4c619b7d61…22f4fa

← previous block·next block →recent activity