← previous blocknext block →recent activity

Analyzing

Block #85,536,710

31 transactions · 20 stateful · 2026-07-04 11:36:48 UTC

Parallelism

84/100

Blocked

35%

Avg conflicts / tx

0.32

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #85,536,710  ·  31 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x17606ba6…1b6e

0x754704…b603

8 touches
6 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

6 touches
3 conflicts

0x01e7b865…6e6e

0x188d58…ea8e

6 touches
3 conflicts

0x74fa2096…56ea

0x754704…b603

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x5e83647d…9707

0xd32edf…ff58

3 touches
1 conflict

0x776b206d…6cf9

0x3bd359…433a

3 touches
1 conflict

0x00f7e3b7…e015

0x188d58…ea8e

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)

6 conflicts on slot 0x17606ba612…ea1b6e

← previous block·next block →recent activity