← previous blocknext block →recent activity

Analyzing

Block #99,813,790

17 transactions · 17 stateful · 2026-08-28 05:21:17 UTC

Parallelism

88/100

Blocked

29%

Avg conflicts / tx

0.29

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #99,813,790  ·  17 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

4 touches
1 conflict

0x6ba0351f…b71e

0x34b655…2a6f

4 touches
1 conflict

0xcc8b6d32…6601

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x40c49f…2af0

4 touches
1 conflict

0x2a07e64e…fe77

0x754704…b603

4 touches
1 conflict

0x00000000…0008

0x8964d7…10f8

4 touches
1 conflict

0x2319fc75…56df

0x8964d7…10f8

4 touches
1 conflict

0x2319fc75…56e0

0x8964d7…10f8

3 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

1 conflict on slot 0x0000000000…00003d

← previous block·next block →recent activity