← previous blocknext block →recent activity

Analyzing

Block #100,734,092

24 transactions · 24 stateful · 2026-08-31 10:38:13 UTC

Parallelism

79/100

Blocked

33%

Avg conflicts / tx

0.58

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #100,734,092  ·  24 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

8 touches
6 conflicts

0xb26ff3de…9352

0xa6afd3…d132

8 touches
6 conflicts

0x42daad7f…630b

0xa6afd3…d132

8 touches
6 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0x451e482b…7e7d

0x34b655…2a6f

6 touches
3 conflicts

0x8cf3d245…1d0d

0x34ae4d…3fc5

4 touches
1 conflict

0xb05cd4f5…73d0

0x34ae4d…3fc5

4 touches
1 conflict

0xdb067026…9eb8

0x34ae4d…3fc5

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

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity