← previous blocknext block →recent activity

Analyzing

Block #92,590,839

17 transactions · 13 stateful · 2026-08-02 21:02:26 UTC

Parallelism

82/100

Blocked

31%

Avg conflicts / tx

0.29

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #92,590,839  ·  17 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

0xe50f87d9…047c

0x754704…b603

4 touches
1 conflict

0x16e75abd…f3ad

0x34b655…2a6f

4 touches
1 conflict

0x7aa512ae…d2e0

0x754704…b603

4 touches
1 conflict

0x7f03e539…f4cc

0x754704…b603

4 touches
1 conflict

0x424934c8…f2f1

0x34b655…2a6f

4 touches
1 conflict

0x6767539b…f211

0x34b655…2a6f

4 touches
1 conflict

0x6d1b72ee…6b77

0x34b655…2a6f

4 touches
1 conflict

0x6d1b72ee…6b78

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 0xe50f87d9f5…58047c

← previous block·next block →recent activity