← previous blocknext block →recent activity

Analyzing

Block #86,683,560

23 transactions · 20 stateful · 2026-07-09 19:13:07 UTC

Parallelism

87/100

Blocked

30%

Avg conflicts / tx

0.35

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #86,683,560  ·  23 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

0x00000000…003d

0x40c49f…2af0

6 touches
3 conflicts

0x8a35acfb…d1ab

0xb1dbf0…c0d3

6 touches
3 conflicts

0x8a35acfb…d1ac

0xb1dbf0…c0d3

5 touches
3 conflicts

0x4d93ce23…88fb

0x34b655…2a6f

4 touches
1 conflict

0x4e58deff…c5d0

0x34b655…2a6f

4 touches
1 conflict

0x7c7eff13…16db

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0x92385428…6941

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: 0x40c49f17…d22af0

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity