← previous blocknext block →recent activity

Analyzing

Block #95,428,016

25 transactions · 24 stateful · 2026-08-12 19:26:15 UTC

Parallelism

56/100

Blocked

58%

Avg conflicts / tx

1.72

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #95,428,016  ·  25 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0xb2fa1675…4e07

0x34b655…2a6f

10 touches
10 conflicts

0x424934c8…f2f1

0x34b655…2a6f

10 touches
10 conflicts

0xec7d120d…7084

0x34b655…2a6f

8 touches
6 conflicts

0xb3fb9fb5…64db

0x34b655…2a6f

8 touches
6 conflicts

0x10a5a231…be40

0x34b655…2a6f

6 touches
3 conflicts

0x84d69e90…64f2

0x34b655…2a6f

6 touches
3 conflicts

0x957c875f…b3f9

0x34b655…2a6f

6 touches
3 conflicts

0xafb8e71e…9285

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

10 conflicts on slot 0xb2fa1675e0…3c4e07

← previous block·next block →recent activity