← previous blocknext block →recent activity

Analyzing

Block #84,315,001

22 transactions · 19 stateful · 2026-06-28 19:52:21 UTC

Parallelism

86/100

Blocked

32%

Avg conflicts / tx

0.41

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #84,315,001  ·  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

0xda47a23d…57e3

0xa6afd3…d132

6 touches
3 conflicts

0xcffc17bc…3544

0x34b655…2a6f

4 touches
1 conflict

0xb3572c95…9c4a

0x2a68ba…90c5

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x134ea5b5…4601

0x34b655…2a6f

4 touches
1 conflict

0x30ae635d…5e67

0x34b655…2a6f

4 touches
1 conflict

0x454d8940…cfe7

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

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 0xda47a23d34…7157e3

← previous block·next block →recent activity