← previous blocknext block →recent activity

Analyzing

Block #97,669,181

27 transactions · 22 stateful · 2026-08-20 16:15:33 UTC

Parallelism

85/100

Blocked

32%

Avg conflicts / tx

0.41

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #97,669,181  ·  27 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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0xe31cf99d…cb66

0x754704…b603

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x36743f6f…476b

0x3bd359…433a

4 touches
1 conflict

0xcce2fd99…a8eb

0x3bd359…433a

4 touches
1 conflict

0x00000000…0000

0x659bd0…a9da

4 touches
1 conflict

0x00000000…0002

0x659bd0…a9da

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