← previous blocknext block →recent activity

Analyzing

Block #83,202,064

20 transactions · 16 stateful · 2026-06-23 16:08:57 UTC

Parallelism

90/100

Blocked

13%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #83,202,064  ·  20 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

4 touches
1 conflict

0x6f1a10f8…5a04

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0xd7513857…4c08

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xe6d3112d…87ea

0x34b655…2a6f

4 touches
1 conflict

0xf324b405…ca30

0x34b655…2a6f

4 touches
1 conflict

0xffc2f21e…b393

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

1 conflict on slot 0x0000000000…00003d

← previous block·next block →recent activity