← previous blocknext block →recent activity

Analyzing

Block #94,796,812

22 transactions · 19 stateful · 2026-08-10 14:16:57 UTC

Parallelism

86/100

Blocked

32%

Avg conflicts / tx

0.41

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #94,796,812  ·  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

0x6847107a…f468

0xa6afd3…d132

6 touches
3 conflicts

0x03aa8b26…118a

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0x0dd3d3cd…7281

0x34b655…2a6f

4 touches
1 conflict

0x0fac8c4a…8f90

0x34b655…2a6f

4 touches
1 conflict

0x310afe2c…83e1

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0xad6a4fb2…1e6f

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 0x6847107ab3…05f468

← previous block·next block →recent activity