← previous blocknext block →recent activity

Analyzing

Block #94,717,822

17 transactions · 16 stateful · 2026-08-10 07:38:10 UTC

Parallelism

82/100

Blocked

38%

Avg conflicts / tx

0.41

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #94,717,822  ·  17 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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xb33ff823…1188

0x065c9d…c394

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x00ddbbf2…4588

0x34b655…2a6f

4 touches
1 conflict

0x04095623…2e2a

0x34b655…2a6f

4 touches
1 conflict

0x152f8e3d…3da0

0x34b655…2a6f

4 touches
1 conflict

0x1f6f8ff8…a5d4

0x34b655…2a6f

4 touches
1 conflict

0x1f6f8ff8…a5d5

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 0x0000000000…00003d

← previous block·next block →recent activity