← previous blocknext block →recent activity

Analyzing

Block #95,393,922

26 transactions · 24 stateful · 2026-08-12 16:33:56 UTC

Parallelism

65/100

Blocked

38%

Avg conflicts / tx

1.54

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #95,393,922  ·  26 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

0xbcbf5d09…8bac

0x34b655…2a6f

16 touches
28 conflicts

0x6c0d708e…f3d2

0x34b655…2a6f

12 touches
15 conflicts

0xe8eae8a3…bacc

0x34b655…2a6f

12 touches
15 conflicts

0xca713a22…3083

0x34b655…2a6f

6 touches
3 conflicts

0x03e80e37…168a

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x74e46435…fdcd

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