← previous blocknext block →recent activity

Analyzing

Block #94,468,266

16 transactions · 16 stateful · 2026-08-09 10:42:56 UTC

Parallelism

56/100

Blocked

56%

Avg conflicts / tx

1.56

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #94,468,266  ·  16 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

14 touches
21 conflicts

0x002fed35…79fa

0x2a68ba…90c5

10 touches
10 conflicts

0x00642b74…139a

0x065c9d…c394

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x81538350…62fd

0x34b655…2a6f

6 touches
3 conflicts

0x6f4c128b…5a33

0x34b655…2a6f

4 touches
1 conflict

0x8a4ab7ad…876a

0x34b655…2a6f

4 touches
1 conflict

0x8f361903…8677

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)

21 conflicts on slot 0xa1087a5ca6…0a66c4

← previous block·next block →recent activity