← previous blocknext block →recent activity

Analyzing

Block #94,490,518

22 transactions · 17 stateful · 2026-08-09 12:34:54 UTC

Parallelism

68/100

Blocked

47%

Avg conflicts / tx

0.95

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #94,490,518  ·  22 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x6669bc63…eef2

0x065c9d…c394

12 touches
15 conflicts

0x002fed35…79fa

0x2a68ba…90c5

12 touches
15 conflicts

0xa1087a5c…66c4

0x754704…b603

10 touches
10 conflicts

0x70eec2ed…f791

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x09106a95…1467

0x33176b…e078

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001c

0x1b6862…e19c

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 0x6669bc637c…d6eef2

← previous block·next block →recent activity