← previous blocknext block →recent activity

Analyzing

Block #97,479,154

19 transactions · 17 stateful · 2026-08-20 00:10:17 UTC

Parallelism

84/100

Blocked

35%

Avg conflicts / tx

0.42

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #97,479,154  ·  19 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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

4 touches
1 conflict

0x1ae0abd5…8a3b

0x34b655…2a6f

4 touches
1 conflict

0x21ca7579…1a1e

0x34b655…2a6f

4 touches
1 conflict

0x2bfc672f…4d28

0x34b655…2a6f

4 touches
1 conflict

0x2bfc672f…4d29

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 0x0000000000…00003d

← previous block·next block →recent activity