← previous blocknext block →recent activity

Analyzing

Block #98,387,928

24 transactions · 19 stateful · 2026-08-23 04:50:42 UTC

Parallelism

88/100

Blocked

37%

Avg conflicts / tx

0.38

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #98,387,928  ·  24 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

0x5e2bd0c1…7ca2

0xa6afd3…d132

6 touches
3 conflicts

0x00000000…0002

0xbb3f3c…e046

4 touches
1 conflict

0xa60eabc0…9f8c

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0xd0f6f4f2…dffa

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0xa6afd3…d132

4 touches
1 conflict

0x892daf6e…48d8

0x065c9d…c394

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-WETH/USDC

3 conflicts on slot 0x5e2bd0c1f4…f57ca2

← previous block·next block →recent activity