← previous blocknext block →recent activity

Analyzing

Block #86,446,304

23 transactions · 17 stateful · 2026-07-08 16:44:42 UTC

Parallelism

83/100

Blocked

35%

Avg conflicts / tx

0.3

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,446,304  ·  23 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

6 touches
3 conflicts

0x040a92ef…fd75

0x34b655…2a6f

4 touches
1 conflict

0x08a5c23d…ca1e

0x34b655…2a6f

4 touches
1 conflict

0x129e21c6…40c1

0x34b655…2a6f

4 touches
1 conflict

0x157dbfb2…4089

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x2961cb84…a044

0x34b655…2a6f

4 touches
1 conflict

0x321eac33…6aca

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

3 conflicts on slot 0xfaef08b108…f90696

← previous block·next block →recent activity