← previous blocknext block →recent activity

Analyzing

Block #86,709,675

23 transactions · 19 stateful · 2026-07-09 22:07:17 UTC

Parallelism

70/100

Blocked

47%

Avg conflicts / tx

0.87

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #86,709,675  ·  23 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

8 touches
6 conflicts

0x70ff9262…8d80

0x34b655…2a6f

8 touches
6 conflicts

0x2d2ecca1…2d77

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x56b5f5c0…a3ad

0x34b655…2a6f

6 touches
3 conflicts

0xc3b45cfb…d185

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xded7831c…3c4a

0x34b655…2a6f

6 touches
3 conflicts

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

6 conflicts on slot 0xfaef08b108…f90696

← previous block·next block →recent activity