← previous blocknext block →recent activity

Analyzing

Block #94,990,927

11 transactions · 11 stateful · 2026-08-11 06:33:20 UTC

Parallelism

82/100

Blocked

27%

Avg conflicts / tx

0.27

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #94,990,927  ·  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

0x170e4e4c…2b90

0x34b655…2a6f

4 touches
1 conflict

0x7ee6007b…fd68

0x34b655…2a6f

4 touches
1 conflict

0x85d4c7be…173a

0x34b655…2a6f

4 touches
1 conflict

0xaf4da2bc…8724

0x34b655…2a6f

4 touches
1 conflict

0xc6589a05…e1be

0x34b655…2a6f

4 touches
1 conflict

0xd2e35622…f491

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

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