← previous blocknext block →recent activity

Analyzing

Block #95,076,490

20 transactions · 19 stateful · 2026-08-11 13:44:32 UTC

Parallelism

60/100

Blocked

58%

Avg conflicts / tx

1.75

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #95,076,490  ·  20 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x08024b2c…d265

0x34b655…2a6f

10 touches
10 conflicts

0x8eef368f…aa21

0x34b655…2a6f

8 touches
6 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

8 touches
6 conflicts

0x1e222bbc…3290

0x34b655…2a6f

8 touches
6 conflicts

0x734ee320…caae

0x34b655…2a6f

6 touches
3 conflicts

0xd8bc53a3…c2fe

0x34b655…2a6f

6 touches
3 conflicts

0xd7668c61…55f8

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