← previous blocknext block →recent activity

Analyzing

Block #86,980,833

23 transactions · 22 stateful · 2026-07-11 04:19:32 UTC

Parallelism

78/100

Blocked

36%

Avg conflicts / tx

0.65

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #86,980,833  ·  23 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

8 touches
6 conflicts

0x8a35acfb…d1aa

0xb1dbf0…c0d3

8 touches
6 conflicts

0x52e69143…95ad

0x065c9d…c394

6 touches
3 conflicts

0xce827910…ff22

0x065c9d…c394

6 touches
3 conflicts

0x8a35acfb…d1a9

0xb1dbf0…c0d3

6 touches
3 conflicts

0xb6ed530c…d450

0x34b655…2a6f

4 touches
1 conflict

0xec1d7176…6f5e

0x34b655…2a6f

4 touches
1 conflict

0xfaef08b1…0696

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

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity