← previous blocknext block →recent activity

Analyzing

Block #86,767,595

27 transactions · 21 stateful · 2026-07-10 04:34:21 UTC

Parallelism

85/100

Blocked

33%

Avg conflicts / tx

0.41

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,767,595  ·  27 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

0xec7fe04a…3c56

0x34b655…2a6f

6 touches
3 conflicts

0x5beb3e40…7258

0x34b655…2a6f

4 touches
1 conflict

0x5fee1ba0…2520

0x34b655…2a6f

4 touches
1 conflict

0x727fbce7…0c80

0x34b655…2a6f

4 touches
1 conflict

0x7da56943…9753

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0x920cdc4c…6283

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