← previous blocknext block →recent activity

Analyzing

Block #95,404,610

12 transactions · 11 stateful · 2026-08-12 17:27:59 UTC

Parallelism

67/100

Blocked

45%

Avg conflicts / tx

0.58

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #95,404,610  ·  12 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x2210fbde…49cc

0x34b655…2a6f

6 touches
3 conflicts

0xe9452241…95a3

0x34b655…2a6f

6 touches
3 conflicts

0x3cd30038…c5af

0x34b655…2a6f

4 touches
1 conflict

0x42e917f7…ed8c

0x34b655…2a6f

4 touches
1 conflict

0x4755fafb…859b

0x34b655…2a6f

4 touches
1 conflict

0x6e6a8155…9636

0x34b655…2a6f

4 touches
1 conflict

0x7239a7a0…e541

0x34b655…2a6f

4 touches
1 conflict

0x84d74093…7808

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

3 conflicts on slot 0x2210fbde2a…3849cc

← previous block·next block →recent activity