← previous blocknext block →recent activity

Analyzing

Block #97,991,384

21 transactions · 19 stateful · 2026-08-21 19:34:27 UTC

Parallelism

71/100

Blocked

42%

Avg conflicts / tx

0.43

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #97,991,384  ·  21 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xe5bb3628…e5f1

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0007

0x340143…768f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xaa6eeeef…cde7

0x34b655…2a6f

4 touches
1 conflict

0xca841faa…486a

0x34b655…2a6f

4 touches
1 conflict

0x14cc77c7…69c4

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