← previous blocknext block →recent activity

Analyzing

Block #95,592,294

16 transactions · 16 stateful · 2026-08-13 09:12:33 UTC

Parallelism

75/100

Blocked

56%

Avg conflicts / tx

0.94

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #95,592,294  ·  16 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

0x212003dc…a249

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x326a02b5…8dad

0x34b655…2a6f

6 touches
3 conflicts

0x6fbc2e5a…e69c

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0x5d7e0e69…e6d2

0x34b655…2a6f

6 touches
3 conflicts

0x6f1a10f8…5a04

0x34b655…2a6f

6 touches
3 conflicts

0x966e45cf…0f25

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

6 conflicts on slot 0x212003dc80…ffa249

← previous block·next block →recent activity