← previous blocknext block →recent activity

Analyzing

Block #85,184,014

34 transactions · 22 stateful · 2026-07-02 20:28:01 UTC

Parallelism

85/100

Blocked

32%

Avg conflicts / tx

0.44

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #85,184,014  ·  34 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

0x9ff176a9…152e

0x065c9d…c394

10 touches
10 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x5540f956…69e8

0x065c9d…c394

6 touches
3 conflicts

0x0c59008d…dec5

0xd32edf…ff58

5 touches
3 conflicts

0x002fed35…79fa

0x2a68ba…90c5

4 touches
1 conflict

0x7d42dc8b…fdb6

0x2a68ba…90c5

4 touches
1 conflict

0x92d610a6…9a40

0x2a68ba…90c5

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

10 conflicts on slot 0x9ff176a9ad…67152e

← previous block·next block →recent activity