← previous blocknext block →recent activity

Analyzing

Block #95,268,167

19 transactions · 17 stateful · 2026-08-12 05:57:26 UTC

Parallelism

74/100

Blocked

47%

Avg conflicts / tx

0.84

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #95,268,167  ·  19 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xbde524f4…43bf

0x34b655…2a6f

10 touches
10 conflicts

0x29cac3f0…d958

0x34b655…2a6f

7 touches
6 conflicts

0x2b54cadb…4425

0xd18b7e…414b

6 touches
3 conflicts

0x00000000…00c9

0x34b655…2a6f

6 touches
3 conflicts

0xd106eb58…b2b1

0x34b655…2a6f

6 touches
3 conflicts

0xf4f18a3d…61d4

0x34b655…2a6f

6 touches
3 conflicts

0x62ee07b8…f615

0x40c49f…2af0

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

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 0xbde524f475…b143bf

← previous block·next block →recent activity