← previous blocknext block →recent activity

Analyzing

Block #98,778,393

23 transactions · 21 stateful · 2026-08-24 14:11:31 UTC

Parallelism

87/100

Blocked

24%

Avg conflicts / tx

0.3

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #98,778,393  ·  23 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

0xa6afd3…d132

6 touches
3 conflicts

0x35680f34…0302

0xa6afd3…d132

4 touches
1 conflict

0x00000000…004c

0x80c745…7210

4 touches
1 conflict

0x080c3a8a…3088

0x34b655…2a6f

4 touches
1 conflict

0x191eae88…6e80

0x34b655…2a6f

4 touches
1 conflict

0x469dac8d…3411

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity