← previous blocknext block →recent activity

Analyzing

Block #98,506,274

25 transactions · 17 stateful · 2026-08-23 14:47:46 UTC

Parallelism

88/100

Blocked

35%

Avg conflicts / tx

0.28

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #98,506,274  ·  25 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

0x0161566e…abb2

0xa6afd3…d132

6 touches
3 conflicts

0xc45e4fb5…7cc3

0xa6afd3…d132

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0x5778d110…d2e6

0xc8689a…ee79

4 touches
1 conflict

0xd6bd849a…5597

0x2a68ba…90c5

4 touches
1 conflict

0x10d80fee…dbda

0x2b46c0…1669

4 touches
1 conflict

0x40970e69…da50

0x2b46c0…1669

4 touches
1 conflict

0xdb067026…9eb8

0x2b46c0…1669

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 0x0161566e2a…d7abb2

← previous block·next block →recent activity