← previous blocknext block →recent activity

Analyzing

Block #86,627,203

24 transactions · 16 stateful · 2026-07-09 12:55:24 UTC

Parallelism

75/100

Blocked

50%

Avg conflicts / tx

0.75

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #86,627,203  ·  24 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xfaef08b1…0696

0x34b655…2a6f

12 touches
15 conflicts

0x1c796c6b…064e

0x34b655…2a6f

4 touches
1 conflict

0x2b268fa9…eba2

0x34b655…2a6f

4 touches
1 conflict

0x2c0b8a5f…9d30

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x7b020c86…6980

0x34b655…2a6f

4 touches
1 conflict

0x826cce18…251c

0x34b655…2a6f

4 touches
1 conflict

0x9a36cb2e…0929

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: Perpl

15 conflicts on slot 0xfaef08b108…f90696

← previous block·next block →recent activity