← previous blocknext block →recent activity

Analyzing

Block #97,493,839

16 transactions · 15 stateful · 2026-08-20 01:24:10 UTC

Parallelism

75/100

Blocked

40%

Avg conflicts / tx

0.69

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #97,493,839  ·  16 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

0x6b9aa7a3…3167

0x065c9d…c394

6 touches
3 conflicts

0xf7bfb5fd…cb38

0x34b655…2a6f

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x713db58f…6ff9

0x34b655…2a6f

6 touches
3 conflicts

0x002fed35…79fa

0x2a68ba…90c5

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xb3fb9fb5…64db

0x34b655…2a6f

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 0x6b9aa7a372…a13167

← previous block·next block →recent activity