← previous blocknext block →recent activity

Analyzing

Block #90,397,397

18 transactions · 17 stateful · 2026-07-26 05:00:27 UTC

Parallelism

61/100

Blocked

53%

Avg conflicts / tx

1.39

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #90,397,397  ·  18 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

0x1bff683e…7ecb

0x754704…b603

14 touches
21 conflicts

0x2f10b475…59fd

0x0a2fbf…29b1

12 touches
15 conflicts

0x2f10b475…5a00

0x0a2fbf…29b1

12 touches
15 conflicts

0x00000000…0005

0x370e2e…63b4

12 touches
15 conflicts

0x2f10b475…59fc

0x0a2fbf…29b1

12 touches
15 conflicts

0x55b4e430…44cb

0x754704…b603

12 touches
15 conflicts

0x00000000…0006

0x0a2fbf…29b1

12 touches
15 conflicts

0x6d7c7ee9…0cea

0x0a2fbf…29b1

12 touches
15 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)

21 conflicts on slot 0x1bff683e61…e67ecb

← previous block·next block →recent activity