← previous blocknext block →recent activity

Analyzing

Block #95,074,858

26 transactions · 22 stateful · 2026-08-11 13:36:19 UTC

Parallelism

62/100

Blocked

50%

Avg conflicts / tx

1.5

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #95,074,858  ·  26 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

0xafb8e71e…9285

0x34b655…2a6f

14 touches
21 conflicts

0x424934c8…f2f1

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xac2a0273…721b

0x34b655…2a6f

8 touches
6 conflicts

0x4c676afe…440e

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x216ffe66…1f94

0x34b655…2a6f

6 touches
3 conflicts

0x3270f906…a0e9

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 0xafb8e71eb0…ec9285

← previous block·next block →recent activity