← previous blocknext block →recent activity

Analyzing

Block #95,111,876

17 transactions · 17 stateful · 2026-08-11 16:42:34 UTC

Parallelism

59/100

Blocked

53%

Avg conflicts / tx

1.47

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #95,111,876  ·  17 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xe26aee7b…f52b

0x34b655…2a6f

12 touches
15 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

8 touches
6 conflicts

0xacd1b162…bee6

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0xe8eae8a3…bacc

0x34b655…2a6f

6 touches
3 conflicts

0x0a2131b3…455e

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xa07e7b13…7513

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

15 conflicts on slot 0xe26aee7b78…9ff52b

← previous block·next block →recent activity