← previous blocknext block →recent activity

Analyzing

Block #99,456,312

22 transactions · 21 stateful · 2026-08-26 23:09:45 UTC

Parallelism

86/100

Blocked

33%

Avg conflicts / tx

0.45

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #99,456,312  ·  22 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

0xbd22d0fc…64fd

0x34b655…2a6f

6 touches
3 conflicts

0x359866c7…de7b

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x05d19874…7b4e

0xa6afd3…d132

4 touches
1 conflict

0x752d9ee0…e490

0x34b655…2a6f

4 touches
1 conflict

0x61979b3c…1533

0x34b655…2a6f

4 touches
1 conflict

0x6114c036…5015

0x34b655…2a6f

2 touches
0 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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity