← previous blocknext block →recent activity

Analyzing

Block #95,528,192

16 transactions · 15 stateful · 2026-08-13 03:50:08 UTC

Parallelism

81/100

Blocked

33%

Avg conflicts / tx

0.44

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #95,528,192  ·  16 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x11b69a7e…334e

0xee8c0e…1242

4 touches
1 conflict

0x08636046…e60f

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x60e67008…f6aa

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x8cd684d0…c3cb

0x34b655…2a6f

4 touches
1 conflict

0xca841faa…486a

0x34b655…2a6f

4 touches
1 conflict

0xea3b49a7…24d7

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: Wrapped Ether (WETH)

1 conflict on slot 0x11b69a7ea1…83334e

← previous block·next block →recent activity