← previous blocknext block →recent activity

Analyzing

Block #86,660,338

21 transactions · 18 stateful · 2026-07-09 16:38:06 UTC

Parallelism

81/100

Blocked

44%

Avg conflicts / tx

0.57

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,660,338  ·  21 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

0xfaef08b1…0696

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x8a35acfb…d1a8

0xb1dbf0…c0d3

5 touches
3 conflicts

0x250c8181…eef2

0x34b655…2a6f

4 touches
1 conflict

0x2d7ea048…d78e

0x34b655…2a6f

4 touches
1 conflict

0x3a2a8323…3f40

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x485ae99d…f26f

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

6 conflicts on slot 0xfaef08b108…f90696

← previous block·next block →recent activity