← previous blocknext block →recent activity

Analyzing

Block #95,372,064

26 transactions · 21 stateful · 2026-08-12 14:43:13 UTC

Parallelism

88/100

Blocked

24%

Avg conflicts / tx

0.27

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #95,372,064  ·  26 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x1b25f260…c429

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…00c9

0x34b655…2a6f

6 touches
3 conflicts

0x10a5a231…be40

0x34b655…2a6f

6 touches
3 conflicts

0xfc34f3ff…aedb

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…641f

0x34b655…2a6f

6 touches
3 conflicts

0xcf6c1a79…b07f

0x34b655…2a6f

6 touches
3 conflicts

0x320701d5…f9f4

0x34b655…2a6f

4 touches
1 conflict

0x326a02b5…8dad

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 0x1b25f26097…52c429

← previous block·next block →recent activity