← previous blocknext block →recent activity

Analyzing

Block #83,877,133

10 transactions · 9 stateful · 2026-06-26 19:15:22 UTC

Parallelism

80/100

Blocked

33%

Avg conflicts / tx

0.4

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #83,877,133  ·  10 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

0x7b7af531…48f1

0xa6afd3…d132

4 touches
1 conflict

0x785889c9…0603

0x34b655…2a6f

4 touches
1 conflict

0x829dc0b1…a3cf

0x34b655…2a6f

4 touches
1 conflict

0xb6aedce9…a483

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xcbd23469…a4df

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xfadc118d…5d64

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 0x7b7af53137…5748f1

← previous block·next block →recent activity