← previous blocknext block →recent activity

Analyzing

Block #83,889,267

10 transactions · 9 stateful · 2026-06-26 20:36:16 UTC

Parallelism

80/100

Blocked

22%

Avg conflicts / tx

0.2

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #83,889,267  ·  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

0x00000000…003d

0xa6afd3…d132

4 touches
1 conflict

0x552c9086…5ad8

0x34b655…2a6f

4 touches
1 conflict

0x6f58168d…ea24

0x34b655…2a6f

4 touches
1 conflict

0x7506443a…4820

0x34b655…2a6f

4 touches
1 conflict

0x98fc5672…13c7

0x34b655…2a6f

4 touches
1 conflict

0xa1571d54…ae41

0x34b655…2a6f

4 touches
1 conflict

0xc0b9bd73…7f1c

0x34b655…2a6f

4 touches
1 conflict

0xd0e9513a…4519

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