← previous blocknext block →recent activity

Analyzing

Block #94,852,081

21 transactions · 18 stateful · 2026-08-10 18:55:01 UTC

Parallelism

86/100

Blocked

28%

Avg conflicts / tx

0.38

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #94,852,081  ·  21 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

0x160f117d…8e90

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x840d3ab7…c8c4

0x34b655…2a6f

4 touches
1 conflict

0x91b0f8ed…6bd6

0x34b655…2a6f

4 touches
1 conflict

0x91b0f8ed…6bd7

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0xb33ff823…1188

0x065c9d…c394

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

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 0x160f117d43…518e90

← previous block·next block →recent activity