← previous blocknext block →recent activity

Analyzing

Block #90,497,695

12 transactions · 10 stateful · 2026-07-26 13:30:00 UTC

Parallelism

75/100

Blocked

40%

Avg conflicts / tx

0.58

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #90,497,695  ·  12 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

0x42041fec…bd86

0x754704…b603

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x79e8f935…c3b6

0x34b655…2a6f

4 touches
1 conflict

0xb444b9b5…9c7b

0x34b655…2a6f

4 touches
1 conflict

0xedd51a10…d1fa

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

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)

3 conflicts on slot 0x42041feca2…afbd86

← previous block·next block →recent activity