← previous blocknext block →recent activity

Analyzing

Block #95,073,963

22 transactions · 19 stateful · 2026-08-11 13:31:49 UTC

Parallelism

82/100

Blocked

42%

Avg conflicts / tx

0.64

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #95,073,963  ·  22 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

0x4cabb80a…46bf

0x34b655…2a6f

8 touches
6 conflicts

0xec7d120d…7084

0x34b655…2a6f

6 touches
3 conflicts

0x94907e1c…f808

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xdb067026…9eb8

0x2b46c0…1669

4 touches
1 conflict

0x2c145401…09fd

0x34b655…2a6f

4 touches
1 conflict

0x34731dbd…e467

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

6 conflicts on slot 0x4cabb80a0e…7546bf

← previous block·next block →recent activity