← previous blocknext block →recent activity

Analyzing

Block #84,259,397

15 transactions · 14 stateful · 2026-06-28 13:41:49 UTC

Parallelism

80/100

Blocked

43%

Avg conflicts / tx

0.47

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #84,259,397  ·  15 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

0x7b7af531…48f1

0xa6afd3…d132

4 touches
1 conflict

0xb3572c95…9c4a

0x2a68ba…90c5

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x6ac6d1bf…8b19

0x34b655…2a6f

4 touches
1 conflict

0x6f132c01…cdcc

0x34b655…2a6f

4 touches
1 conflict

0x6f132c01…cdcd

0x34b655…2a6f

4 touches
1 conflict

0xe99d8e68…a16e

0x34b655…2a6f

4 touches
1 conflict

0xfb3e3a2a…42f3

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