← previous blocknext block →recent activity

Analyzing

Block #95,625,669

17 transactions · 17 stateful · 2026-08-13 12:00:26 UTC

Parallelism

41/100

Blocked

65%

Avg conflicts / tx

1.88

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #95,625,669  ·  17 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

14 touches
21 conflicts

0x4c619b7d…f4fa

0x34b655…2a6f

10 touches
10 conflicts

0x482471ad…122f

0x34b655…2a6f

10 touches
10 conflicts

0xc30561d8…c5cc

0x34b655…2a6f

8 touches
6 conflicts

0xca841faa…486a

0x34b655…2a6f

8 touches
6 conflicts

0xfc8cd993…5c11

0x34b655…2a6f

6 touches
3 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0xbfabda7b…a0d0

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

21 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity