← previous blocknext block →recent activity

Analyzing

Block #98,764,642

28 transactions · 19 stateful · 2026-08-24 13:02:20 UTC

Parallelism

89/100

Blocked

32%

Avg conflicts / tx

0.29

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #98,764,642  ·  28 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

0x99cef18b…a4fb

0x065c9d…c394

6 touches
3 conflicts

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…0036

0x35a73b…6042

6 touches
3 conflicts

0xaf831072…51d5

0x69a5f9…2fef

6 touches
3 conflicts

0xaf831072…51d6

0x69a5f9…2fef

6 touches
3 conflicts

0xaf831072…51dc

0x69a5f9…2fef

6 touches
3 conflicts

0x2ef1d89b…196d

0x754704…b603

6 touches
3 conflicts

0x00000000…0002

0xbb3f3c…e046

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 0x99cef18be7…fba4fb

← previous block·next block →recent activity