← previous blocknext block →recent activity

Analyzing

Block #94,759,544

21 transactions · 18 stateful · 2026-08-10 11:09:30 UTC

Parallelism

71/100

Blocked

44%

Avg conflicts / tx

0.67

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #94,759,544  ·  21 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

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0x1404c7b4…1537

0xd32edf…ff58

5 touches
3 conflicts

0x47501790…1682

0x065c9d…c394

5 touches
3 conflicts

0xa9f633f5…7480

0x065c9d…c394

4 touches
1 conflict

0x2d075bdf…9bd7

0x065c9d…c394

4 touches
1 conflict

0x52e69143…95ad

0x065c9d…c394

4 touches
1 conflict

0x8e40b50a…74fe

0x065c9d…c394

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

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity