← previous blocknext block →recent activity

Analyzing

Block #94,064,685

14 transactions · 14 stateful · 2026-08-08 00:37:12 UTC

Parallelism

79/100

Blocked

14%

Avg conflicts / tx

0.21

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #94,064,685  ·  14 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

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x002fed35…79fa

0x2a68ba…90c5

4 touches
1 conflict

0xc6e5cb9b…4999

0x065c9d…c394

3 touches
1 conflict

0x0e71cd04…ded1

0x34b655…2a6f

2 touches
0 conflicts

0x12aab623…c2fd

0x34b655…2a6f

2 touches
0 conflicts

0x1f00a5b3…bf76

0x34b655…2a6f

2 touches
0 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

2 touches
0 conflicts

0x44614953…f05c

0x34b655…2a6f

2 touches
0 conflicts

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