← previous blocknext block →recent activity

Analyzing

Block #95,524,086

20 transactions · 18 stateful · 2026-08-13 03:29:29 UTC

Parallelism

75/100

Blocked

44%

Avg conflicts / tx

0.75

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #95,524,086  ·  20 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

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x6a95ba16…0c9e

0x34b655…2a6f

6 touches
3 conflicts

0x1a5d321d…a474

0x34b655…2a6f

6 touches
3 conflicts

0x27f75f20…525c

0x34b655…2a6f

4 touches
1 conflict

0x320701d5…f9f4

0x34b655…2a6f

4 touches
1 conflict

0x947bb79d…6458

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 0xc824469a90…af6425

← previous block·next block →recent activity