← previous blocknext block →recent activity

Analyzing

Block #86,620,016

26 transactions · 22 stateful · 2026-07-09 12:07:27 UTC

Parallelism

85/100

Blocked

27%

Avg conflicts / tx

0.35

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,620,016  ·  26 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x8a35acfb…d1aa

0xb1dbf0…c0d3

6 touches
3 conflicts

0x8a35acfb…d1ab

0xb1dbf0…c0d3

6 touches
3 conflicts

0x143dba04…1b98

0xb1dbf0…c0d3

6 touches
3 conflicts

0x1e451306…7993

0xb1dbf0…c0d3

6 touches
3 conflicts

0x4caf91f9…8ab5

0x34b655…2a6f

4 touches
1 conflict

0xa29182a1…c12c

0x34b655…2a6f

4 touches
1 conflict

0x8a35acfb…d1a0

0xb1dbf0…c0d3

4 touches
1 conflict

0xd98b3c10…67b8

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: 0xb1dbf05f…b1c0d3

3 conflicts on slot 0x8a35acfbc1…6bd1aa

← previous block·next block →recent activity