← previous blocknext block →recent activity

Analyzing

Block #94,299,466

18 transactions · 18 stateful · 2026-08-08 20:25:07 UTC

Parallelism

67/100

Blocked

56%

Avg conflicts / tx

1.28

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #94,299,466  ·  18 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

10 touches
10 conflicts

0xca841faa…486a

0x34b655…2a6f

8 touches
6 conflicts

0x11b69a7e…334e

0xee8c0e…1242

8 touches
6 conflicts

0x002fed35…79fa

0x2a68ba…90c5

6 touches
3 conflicts

0x2a9e9bd1…5368

0x2a68ba…90c5

6 touches
3 conflicts

0xa86351b8…2c5a

0x34b655…2a6f

6 touches
3 conflicts

0xe4cc31f2…78c2

0xa6afd3…d132

5 touches
3 conflicts

0xd7e4626c…e1bb

0xa6afd3…d132

5 touches
3 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)

10 conflicts on slot 0xa1087a5ca6…0a66c4

← previous block·next block →recent activity