← previous blocknext block →recent activity

Analyzing

Block #93,580,883

21 transactions · 19 stateful · 2026-08-06 08:04:10 UTC

Parallelism

76/100

Blocked

47%

Avg conflicts / tx

0.67

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #93,580,883  ·  21 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

0x890a1db9…1712

0xa6afd3…d132

6 touches
3 conflicts

0x52b477bc…7ccf

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0x1bf8d2af…d140

0x34b655…2a6f

4 touches
1 conflict

0x2fdfa032…139c

0x34b655…2a6f

4 touches
1 conflict

0x859c92cc…430b

0x34b655…2a6f

4 touches
1 conflict

0xb1b58b33…874f

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 0x890a1db90d…dc1712

← previous block·next block →recent activity