← previous blocknext block →recent activity

Analyzing

Block #95,539,392

11 transactions · 11 stateful · 2026-08-13 04:46:29 UTC

Parallelism

82/100

Blocked

27%

Avg conflicts / tx

0.36

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #95,539,392  ·  11 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

0xdc255d21…c377

0x754704…b603

4 touches
1 conflict

0x28c180e1…f1e2

0x34b655…2a6f

4 touches
1 conflict

0x2fd61111…5bbc

0x34b655…2a6f

4 touches
1 conflict

0x367b69ad…33d8

0x34b655…2a6f

4 touches
1 conflict

0x367b69ad…33d9

0x34b655…2a6f

4 touches
1 conflict

0x458b9085…9ee2

0x34b655…2a6f

4 touches
1 conflict

0x7fb99184…e8bb

0x34b655…2a6f

4 touches
1 conflict

0x8ecc3b8d…bead

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: USDC (USDC)

1 conflict on slot 0xdc255d2170…b4c377

← previous block·next block →recent activity