← previous blocknext block →recent activity

Analyzing

Block #84,351,900

22 transactions · 19 stateful · 2026-06-28 23:58:16 UTC

Parallelism

91/100

Blocked

26%

Avg conflicts / tx

0.27

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #84,351,900  ·  22 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

0x5da4ed2f…283f

0xa6afd3…d132

4 touches
1 conflict

0x13a54fa2…5ae3

0x2a68ba…90c5

4 touches
1 conflict

0x5581d709…ab77

0x2a68ba…90c5

4 touches
1 conflict

0xb3572c95…9c4a

0x2a68ba…90c5

4 touches
1 conflict

0x9e77b752…1238

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0xd2cdfa3f…f071

0x34b655…2a6f

4 touches
1 conflict

0x4c906117…3dd4

0x5afd3e…7620

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 0x5da4ed2fdd…52283f

← previous block·next block →recent activity