← previous blocknext block →recent activity

Analyzing

Block #96,254,921

14 transactions · 11 stateful · 2026-08-15 16:46:58 UTC

Parallelism

86/100

Blocked

27%

Avg conflicts / tx

0.21

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #96,254,921  ·  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

0xc6b1d981…1be2

0xa6afd3…d132

4 touches
1 conflict

0x06726618…fafd

0x34b655…2a6f

4 touches
1 conflict

0x427dec7f…61c6

0x34b655…2a6f

4 touches
1 conflict

0x6f1a10f8…5a04

0x34b655…2a6f

4 touches
1 conflict

0x776b6465…2a06

0x34b655…2a6f

4 touches
1 conflict

0x9c26cddd…9972

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xf324b405…ca30

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: Kuru Exchange: Market-WETH/USDC

1 conflict on slot 0xc6b1d98106…cc1be2

← previous block·next block →recent activity