← previous blocknext block →recent activity

Analyzing

Block #85,130,054

20 transactions · 17 stateful · 2026-07-02 14:28:31 UTC

Parallelism

75/100

Blocked

47%

Avg conflicts / tx

0.55

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #85,130,054  ·  20 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

6 touches
3 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…003d

0x851145…3f07

4 touches
1 conflict

0x7fffd49d…772a

0x34b655…2a6f

4 touches
1 conflict

0xaa99c369…263d

0x34b655…2a6f

4 touches
1 conflict

0xad6a9d21…2ac8

0x34b655…2a6f

4 touches
1 conflict

0xc9730b49…b895

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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity