← previous blocknext block →recent activity

Analyzing

Block #94,481,933

18 transactions · 16 stateful · 2026-08-09 11:51:44 UTC

Parallelism

61/100

Blocked

56%

Avg conflicts / tx

1.33

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #94,481,933  ·  18 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

0xf1522cbe…3390

0x065c9d…c394

14 touches
21 conflicts

0x002fed35…79fa

0x2a68ba…90c5

14 touches
21 conflicts

0xa1087a5c…66c4

0x754704…b603

14 touches
21 conflicts

0x0dd3bdfb…7538

0x34b655…2a6f

4 touches
1 conflict

0x201d7cf1…f7f2

0x34b655…2a6f

4 touches
1 conflict

0x2b75d304…d186

0x34b655…2a6f

4 touches
1 conflict

0x32aa69c7…bdea

0x34b655…2a6f

4 touches
1 conflict

0x3522af60…d679

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

21 conflicts on slot 0xf1522cbe1a…ea3390

← previous block·next block →recent activity