← previous blocknext block →recent activity

Analyzing

Block #92,066,242

20 transactions · 18 stateful · 2026-08-01 01:04:05 UTC

Parallelism

55/100

Blocked

56%

Avg conflicts / tx

1.95

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #92,066,242  ·  20 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0xe1f61186…e2f8

0x754704…b603

18 touches
36 conflicts

0x00000000…0006

0x7b9256…1fb2

18 touches
36 conflicts

0x177211e2…1c2d

0x754704…b603

18 touches
36 conflicts

0x02c545ec…9513

0x7b9256…1fb2

16 touches
28 conflicts

0x1725abb3…3fb7

0x7b9256…1fb2

16 touches
28 conflicts

0x1725abb3…3fb8

0x7b9256…1fb2

16 touches
28 conflicts

0x02c545ec…950f

0x7b9256…1fb2

16 touches
28 conflicts

0x02c545ec…9510

0x7b9256…1fb2

16 touches
28 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)

36 conflicts on slot 0xe1f61186c5…67e2f8

← previous block·next block →recent activity