← previous blocknext block →recent activity

Analyzing

Block #95,593,572

14 transactions · 13 stateful · 2026-08-13 09:18:58 UTC

Parallelism

86/100

Blocked

15%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #95,593,572  ·  14 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

0x91b0f8ed…6bd6

0x34b655…2a6f

4 touches
1 conflict

0x91b0f8ed…6bd7

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

2 touches
0 conflicts

0x344bc09a…942f

0x34b655…2a6f

2 touches
0 conflicts

0x48a0f121…953b

0x34b655…2a6f

2 touches
0 conflicts

0x73670e81…2813

0x34b655…2a6f

2 touches
0 conflicts

0x9a89094e…f5b2

0x34b655…2a6f

2 touches
0 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

1 conflict on slot 0x91b0f8edc5…b76bd6

← previous block·next block →recent activity