← previous blocknext block →recent activity

Analyzing

Block #92,243,342

18 transactions · 17 stateful · 2026-08-01 15:54:45 UTC

Parallelism

83/100

Blocked

35%

Avg conflicts / tx

0.5

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #92,243,342  ·  18 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

0xeaced15b…2221

0x754704…b603

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xc4e19ae4…0788

0xe7cd86…c82d

4 touches
1 conflict

0x00000000…001f

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002f

0x1b6862…e19c

4 touches
1 conflict

0xcb0221be…c2b3

0x34b655…2a6f

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

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)

3 conflicts on slot 0xeaced15b26…bf2221

← previous block·next block →recent activity