← previous blocknext block →recent activity

Analyzing

Block #83,575,260

18 transactions · 17 stateful · 2026-06-25 09:40:52 UTC

Parallelism

78/100

Blocked

41%

Avg conflicts / tx

0.67

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #83,575,260  ·  18 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xbaff104b…3edb

0xa6afd3…d132

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0xe99d8e68…a16e

0x34b655…2a6f

6 touches
3 conflicts

0x15c9b5bf…f732

0x34b655…2a6f

4 touches
1 conflict

0x19ce481d…6c36

0x34b655…2a6f

4 touches
1 conflict

0x2ac54041…4713

0x34b655…2a6f

4 touches
1 conflict

0x65bb8d8c…8bb0

0x34b655…2a6f

4 touches
1 conflict

0xb3fb9fb5…64db

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 0xbaff104b03…863edb

← previous block·next block →recent activity