← previous blocknext block →recent activity

Analyzing

Block #92,310,299

22 transactions · 20 stateful · 2026-08-01 21:31:32 UTC

Parallelism

77/100

Blocked

40%

Avg conflicts / tx

0.55

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #92,310,299  ·  22 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x1d44909b…e905

0xa6afd3…d132

4 touches
1 conflict

0xddd76090…8bce

0x34b655…2a6f

4 touches
1 conflict

0x00ebed49…1e8f

0x34b655…2a6f

4 touches
1 conflict

0xda46a376…f6a6

0x34b655…2a6f

4 touches
1 conflict

0x3f588581…17b6

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

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 0x0000000000…00003d

← previous block·next block →recent activity