← previous blocknext block →recent activity

Analyzing

Block #86,659,050

24 transactions · 18 stateful · 2026-07-09 16:29:31 UTC

Parallelism

79/100

Blocked

44%

Avg conflicts / tx

0.58

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #86,659,050  ·  24 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

0x8a35acfb…d1ab

0xb1dbf0…c0d3

8 touches
6 conflicts

0x8a35acfb…d1ac

0xb1dbf0…c0d3

8 touches
6 conflicts

0xfaef08b1…0696

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x3a2a8323…3f40

0x34b655…2a6f

4 touches
1 conflict

0x48fb2063…4025

0x34b655…2a6f

4 touches
1 conflict

0x548145a9…cfce

0x34b655…2a6f

4 touches
1 conflict

0x5b7d1494…ed87

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

6 conflicts on slot 0x8a35acfbc1…6bd1ab

← previous block·next block →recent activity