← previous blocknext block →recent activity

Analyzing

Block #95,736,335

15 transactions · 12 stateful · 2026-08-13 21:18:06 UTC

Parallelism

80/100

Blocked

58%

Avg conflicts / tx

0.6

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #95,736,335  ·  15 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

0x3708ee99…9745

0x065c9d…c394

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x002fed35…79fa

0x2a68ba…90c5

6 touches
3 conflicts

0x0728ec77…146c

0x34b655…2a6f

6 touches
3 conflicts

0xc85f42b6…6f23

0x34b655…2a6f

4 touches
1 conflict

0x8ec95f2b…f4d7

0x34b655…2a6f

4 touches
1 conflict

0x620b761c…270e

0x34b655…2a6f

4 touches
1 conflict

0xcd176877…2c75

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

3 conflicts on slot 0x3708ee99b7…e39745

← previous block·next block →recent activity