← previous blocknext block →recent activity

Analyzing

Block #92,856,266

22 transactions · 20 stateful · 2026-08-03 19:18:53 UTC

Parallelism

86/100

Blocked

35%

Avg conflicts / tx

0.41

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #92,856,266  ·  22 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

0x1a287886…0266

0xa6afd3…d132

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0x1803586e…d149

0xa6afd3…d132

6 touches
3 conflicts

0x840d3ab7…c8c4

0x34b655…2a6f

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x7e06d07b…36b0

0x34b655…2a6f

4 touches
1 conflict

0x86ffc7db…4b6e

0x34b655…2a6f

4 touches
1 conflict

0xb197665e…4277

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: Kuru Exchange: Market-WETH/USDC

3 conflicts on slot 0x1a287886c0…610266

← previous block·next block →recent activity