← previous blocknext block →recent activity

Analyzing

Block #90,289,514

14 transactions · 12 stateful · 2026-07-25 19:49:00 UTC

Parallelism

79/100

Blocked

33%

Avg conflicts / tx

0.36

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #90,289,514  ·  14 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

0x55b4e430…44cb

0x754704…b603

4 touches
1 conflict

0x97505c03…adce

0x34b655…2a6f

4 touches
1 conflict

0xc39338bf…d0e7

0x34b655…2a6f

4 touches
1 conflict

0xda12e7f3…e890

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0006

0x0a2fbf…29b1

4 touches
1 conflict

0x4b899e34…b9f9

0x0a2fbf…29b1

4 touches
1 conflict

0x4b899e34…b9fa

0x0a2fbf…29b1

4 touches
1 conflict

0x4b899e34…b9fd

0x0a2fbf…29b1

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 0x55b4e430de…d044cb

← previous block·next block →recent activity