← previous blocknext block →recent activity

Analyzing

Block #95,406,672

22 transactions · 21 stateful · 2026-08-12 17:38:24 UTC

Parallelism

73/100

Blocked

33%

Avg conflicts / tx

0.86

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #95,406,672  ·  22 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xf0d45ffd…89cf

0x34b655…2a6f

12 touches
15 conflicts

0x529e53cf…38e4

0xa6afd3…d132

4 touches
1 conflict

0xe69df7e2…3022

0x34b655…2a6f

4 touches
1 conflict

0xefb62c0f…fef8

0x34b655…2a6f

4 touches
1 conflict

0xf5547123…bec8

0x34b655…2a6f

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x08636046…e60f

0x34b655…2a6f

4 touches
1 conflict

0x2e8187e0…ffb6

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 0xf0d45ffdb0…4089cf

← previous block·next block →recent activity