← previous blocknext block →recent activity

Analyzing

Block #99,186,750

21 transactions · 19 stateful · 2026-08-26 00:32:54 UTC

Parallelism

67/100

Blocked

47%

Avg conflicts / tx

1

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #99,186,750  ·  21 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x92f41d1f…4258

0xa6afd3…d132

12 touches
15 conflicts

0x00000000…003d

0xa6afd3…d132

12 touches
15 conflicts

0x889d5e90…929a

0x2a68ba…90c5

8 touches
6 conflicts

0x40970e69…da50

0x2b46c0…1669

6 touches
3 conflicts

0x8cf3d245…1d0d

0x2b46c0…1669

6 touches
3 conflicts

0xb05cd4f5…73d0

0x2b46c0…1669

6 touches
3 conflicts

0x5778d110…d2e6

0xc8689a…ee79

6 touches
3 conflicts

0xd6bd849a…5597

0x2a68ba…90c5

6 touches
3 conflicts

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

15 conflicts on slot 0x92f41d1fe3…854258

← previous block·next block →recent activity