← previous blocknext block →recent activity

Analyzing

Block #83,866,583

20 transactions · 20 stateful · 2026-06-26 18:05:00 UTC

Parallelism

80/100

Blocked

40%

Avg conflicts / tx

0.65

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #83,866,583  ·  20 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

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0x2d5c395b…6b5a

0xa6afd3…d132

6 touches
3 conflicts

0x7c5260f4…bd96

0xa6afd3…d132

6 touches
3 conflicts

0xc73c2ed6…3947

0xd32edf…ff58

5 touches
3 conflicts

0x00000000…0018

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0028

0x1b6862…e19c

4 touches
1 conflict

0xba5743c7…21bf

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

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