← previous blocknext block →recent activity

Analyzing

Block #94,977,956

11 transactions · 9 stateful · 2026-08-11 05:28:05 UTC

Parallelism

82/100

Blocked

22%

Avg conflicts / tx

0.18

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #94,977,956  ·  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

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x323edc8e…ffdf

0x34b655…2a6f

4 touches
1 conflict

0x366c7d57…0ed1

0x34b655…2a6f

4 touches
1 conflict

0x4a6b3039…6a98

0x34b655…2a6f

4 touches
1 conflict

0x65f90aa4…c97f

0x34b655…2a6f

4 touches
1 conflict

0x6f1a10f8…5a04

0x34b655…2a6f

4 touches
1 conflict

0xb17f4dc6…f781

0x34b655…2a6f

4 touches
1 conflict

0xb1dfd5cf…0f25

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 0xa1087a5ca6…0a66c4

← previous block·next block →recent activity