← previous blocknext block →recent activity

Analyzing

Block #84,400,413

20 transactions · 19 stateful · 2026-06-29 05:21:46 UTC

Parallelism

85/100

Blocked

37%

Avg conflicts / tx

0.6

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #84,400,413  ·  20 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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xe99d8e68…a16e

0x34b655…2a6f

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x7d42dc8b…fdb6

0x2a68ba…90c5

4 touches
1 conflict

0x56785e37…a197

0x065c9d…c394

4 touches
1 conflict

0xa9db7b4d…2957

0x40c49f…2af0

4 touches
1 conflict

0x7c6984da…21e5

0x34b655…2a6f

4 touches
1 conflict

0xab86573c…682e

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-MON/USDC

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity