← previous blocknext block →recent activity

Analyzing

Block #99,251,413

17 transactions · 16 stateful · 2026-08-26 05:58:15 UTC

Parallelism

76/100

Blocked

50%

Avg conflicts / tx

0.65

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #99,251,413  ·  17 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x348fda08…7e96

0x065c9d…c394

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0xc8ab31f9…8ce9

0xa6afd3…d132

4 touches
1 conflict

0x261cbea7…e35d

0x34b655…2a6f

4 touches
1 conflict

0x261cbea7…e35e

0x34b655…2a6f

4 touches
1 conflict

0x74ef82ed…eecc

0x34b655…2a6f

4 touches
1 conflict

0xd8ac9c9b…9bcd

0x34b655…2a6f

4 touches
1 conflict

0x177211e2…1c2d

0x754704…b603

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 0x348fda08cf…fc7e96

← previous block·next block →recent activity