← previous blocknext block →recent activity

Analyzing

Block #93,315,041

10 transactions · 8 stateful · 2026-08-05 09:47:41 UTC

Parallelism

80/100

Blocked

25%

Avg conflicts / tx

0.2

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #93,315,041  ·  10 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

4 touches
1 conflict

0x1f6f8ff8…a5d4

0x34b655…2a6f

4 touches
1 conflict

0x1f6f8ff8…a5d5

0x34b655…2a6f

4 touches
1 conflict

0x3e72a2d1…ce0e

0x34b655…2a6f

4 touches
1 conflict

0xbcbf5d09…8bac

0x34b655…2a6f

4 touches
1 conflict

0xc601b84f…92e7

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xdc57bb0d…6fa9

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

1 conflict on slot 0x1a287886c0…610266

← previous block·next block →recent activity