← previous blocknext block →recent activity

Analyzing

Block #92,370,501

20 transactions · 20 stateful · 2026-08-02 02:34:17 UTC

Parallelism

85/100

Blocked

25%

Avg conflicts / tx

0.45

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #92,370,501  ·  20 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

0xe1f61186…e2f8

0x754704…b603

6 touches
3 conflicts

0x00000000…0006

0x7b9256…1fb2

6 touches
3 conflicts

0x0786e18c…3b87

0x7b9256…1fb2

6 touches
3 conflicts

0x0786e18c…3b88

0x7b9256…1fb2

6 touches
3 conflicts

0x0786e18c…3b89

0x7b9256…1fb2

6 touches
3 conflicts

0x2a74ae7b…53b7

0x7b9256…1fb2

6 touches
3 conflicts

0x2a74ae7b…53b8

0x7b9256…1fb2

6 touches
3 conflicts

0x2a74ae7b…53bb

0x7b9256…1fb2

6 touches
3 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)

3 conflicts on slot 0xe1f61186c5…67e2f8

← previous block·next block →recent activity