← previous blocknext block →recent activity

Analyzing

Block #90,546,103

17 transactions · 14 stateful · 2026-07-26 17:33:29 UTC

Parallelism

88/100

Blocked

21%

Avg conflicts / tx

0.18

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #90,546,103  ·  17 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

0x42041fec…bd86

0x754704…b603

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0xbcbf5d09…8bac

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0x3ad2a4a9…109c

0x065c9d…c394

2 touches
0 conflicts

0x9ff176a9…152e

0x065c9d…c394

2 touches
0 conflicts

0xeb2e1a31…faef

0x065c9d…c394

2 touches
0 conflicts

0x11258774…9892

0x2a68ba…90c5

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 0x42041feca2…afbd86

← previous block·next block →recent activity