← previous blocknext block →recent activity

Analyzing

Block #95,151,307

22 transactions · 21 stateful · 2026-08-11 20:00:54 UTC

Parallelism

59/100

Blocked

52%

Avg conflicts / tx

1.77

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #95,151,307  ·  22 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

16 touches
28 conflicts

0x482471ad…122f

0x34b655…2a6f

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x966e45cf…0f25

0x34b655…2a6f

8 touches
6 conflicts

0x0462262d…a368

0x34b655…2a6f

6 touches
3 conflicts

0x4f394483…ff62

0x34b655…2a6f

6 touches
3 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0xc5a1b2fe…5369

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

28 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity