← previous blocknext block →recent activity

Analyzing

Block #99,075,570

23 transactions · 18 stateful · 2026-08-25 15:13:06 UTC

Parallelism

83/100

Blocked

39%

Avg conflicts / tx

0.35

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #99,075,570  ·  23 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

0x41755291…977f

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0xf984d8ab…6e4f

0x34b655…2a6f

4 touches
1 conflict

0x8c49c85c…ee96

0x34b655…2a6f

4 touches
1 conflict

0xbe8cbe85…9c51

0x065c9d…c394

4 touches
1 conflict

0x11258774…9892

0x2a68ba…90c5

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

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 0x4175529119…79977f

← previous block·next block →recent activity