← previous blocknext block →recent activity

Analyzing

Block #85,275,551

14 transactions · 14 stateful · 2026-07-03 06:37:44 UTC

Parallelism

79/100

Blocked

21%

Avg conflicts / tx

0.29

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #85,275,551  ·  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

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0xb5c7c6aa…fdba

0x34b655…2a6f

4 touches
1 conflict

0xd8834cf3…0004

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x0efc210e…70ab

0x34b655…2a6f

4 touches
1 conflict

0x1175233a…64e7

0x34b655…2a6f

4 touches
1 conflict

0x170e4e4c…2b90

0x34b655…2a6f

4 touches
1 conflict

0x1d61a1c5…9fe6

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)

1 conflict on slot 0x17606ba612…ea1b6e

← previous block·next block →recent activity