← previous blocknext block →recent activity

Analyzing

Block #86,608,979

26 transactions · 23 stateful · 2026-07-09 10:53:45 UTC

Parallelism

81/100

Blocked

30%

Avg conflicts / tx

0.38

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #86,608,979  ·  26 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

0xfaef08b1…0696

0x34b655…2a6f

6 touches
3 conflicts

0xca2926e0…61b5

0x34b655…2a6f

6 touches
3 conflicts

0xe5a9274d…78d7

0x34b655…2a6f

6 touches
3 conflicts

0x842389d2…e6ea

0x34b655…2a6f

4 touches
1 conflict

0x88c04dab…63e2

0x34b655…2a6f

4 touches
1 conflict

0xa46242d8…c0a8

0x34b655…2a6f

4 touches
1 conflict

0xacc27c35…6580

0x34b655…2a6f

4 touches
1 conflict

0xc3eedc44…373f

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