← previous blocknext block →recent activity

Analyzing

Block #99,255,395

24 transactions · 21 stateful · 2026-08-26 06:18:17 UTC

Parallelism

88/100

Blocked

29%

Avg conflicts / tx

0.29

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #99,255,395  ·  24 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

0x348fda08…7e96

0x065c9d…c394

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0xd17580f9…ece1

0x754704…b603

4 touches
1 conflict

0x00000000…0002

0xf5b5f7…6d70

4 touches
1 conflict

0x0616f00f…ceed

0xd32edf…ff58

3 touches
1 conflict

0x988e5a19…afe4

0x065c9d…c394

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

2 touches
0 conflicts

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