← previous blocknext block →recent activity

Analyzing

Block #85,178,330

26 transactions · 16 stateful · 2026-07-02 19:50:08 UTC

Parallelism

85/100

Blocked

44%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #85,178,330  ·  26 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x4039b31f…0f4a

0x754704…b603

8 touches
6 conflicts

0xa1087a5c…66c4

0x754704…b603

8 touches
6 conflicts

0xba613030…b33c

0x065c9d…c394

8 touches
6 conflicts

0x00000000…0004

0x5afd3e…7620

8 touches
6 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

8 touches
6 conflicts

0x00000000…0005

0x5afd3e…7620

4 touches
1 conflict

0xf76fd3e7…53cc

0x754704…b603

4 touches
1 conflict

0x00000000…0002

0x04fdea…47d7

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)

6 conflicts on slot 0x4039b31fcf…cb0f4a

← previous block·next block →recent activity