← previous blocknext block →recent activity

Analyzing

Block #86,960,357

19 transactions · 18 stateful · 2026-07-11 02:02:44 UTC

Parallelism

84/100

Blocked

39%

Avg conflicts / tx

0.58

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #86,960,357  ·  19 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

0x49cbdb1b…bda4

0x065c9d…c394

6 touches
3 conflicts

0xfaef08b1…0696

0x34b655…2a6f

6 touches
3 conflicts

0x64aaadbf…f9f3

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x90e113f8…c8f9

0xc8689a…ee79

4 touches
1 conflict

0x6d99ac64…0aa3

0x34b655…2a6f

4 touches
1 conflict

0xb9ec1881…a565

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1542

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 0x49cbdb1b43…f7bda4

← previous block·next block →recent activity