← previous blocknext block →recent activity

Analyzing

Block #95,749,306

20 transactions · 18 stateful · 2026-08-13 22:23:20 UTC

Parallelism

70/100

Blocked

50%

Avg conflicts / tx

1

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #95,749,306  ·  20 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xc3ff36aa…28cf

0x065c9d…c394

12 touches
15 conflicts

0xa1087a5c…66c4

0x754704…b603

12 touches
15 conflicts

0x0778475b…bd75

0x2a68ba…90c5

12 touches
15 conflicts

0xa2478c84…6956

0x754704…b603

4 touches
1 conflict

0x91cdfdeb…7feb

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xe0e00683…e335

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-MON/USDC

15 conflicts on slot 0xc3ff36aa5b…d728cf

← previous block·next block →recent activity