← previous blocknext block →recent activity

Analyzing

Block #95,548,856

16 transactions · 14 stateful · 2026-08-13 05:34:04 UTC

Parallelism

88/100

Blocked

14%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #95,548,856  ·  16 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x9a89094e…f5b2

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xf324b405…ca30

0x34b655…2a6f

4 touches
1 conflict

0xf3a1c372…8786

0x34b655…2a6f

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x052960a0…f32e

0x34b655…2a6f

4 touches
1 conflict

0x0e246445…9e0e

0x34b655…2a6f

4 touches
1 conflict

0x17935a8f…a796

0x34b655…2a6f

4 touches
1 conflict

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

1 conflict on slot 0x9a89094e2b…f6f5b2

← previous block·next block →recent activity