← previous blocknext block →recent activity

Analyzing

Block #94,373,768

19 transactions · 17 stateful · 2026-08-09 02:42:55 UTC

Parallelism

89/100

Blocked

12%

Avg conflicts / tx

0.16

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #94,373,768  ·  19 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

0x0e4000ee…afb9

0x34b655…2a6f

4 touches
1 conflict

0x1b77e6f7…53d7

0x34b655…2a6f

4 touches
1 conflict

0x1dfddec7…1250

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0x8f203394…f2db

0x34b655…2a6f

4 touches
1 conflict

0x8f203394…f2dc

0x34b655…2a6f

4 touches
1 conflict

0x92385428…6941

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