← previous blocknext block →recent activity

Analyzing

Block #86,288,262

21 transactions · 20 stateful · 2026-07-07 23:08:57 UTC

Parallelism

86/100

Blocked

25%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #86,288,262  ·  21 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

0x18cf3003…51d1

0x065c9d…c394

6 touches
3 conflicts

0xcc8faac2…c766

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xfadb0e19…7a27

0x851145…3f07

4 touches
1 conflict

0x3c09f64a…e620

0x34b655…2a6f

4 touches
1 conflict

0x5d036786…b92e

0x34b655…2a6f

4 touches
1 conflict

0x5fcb4c60…8775

0x34b655…2a6f

4 touches
1 conflict

0x7d6b9af1…9a38

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 0x18cf3003ed…9951d1

← previous block·next block →recent activity