← previous blocknext block →recent activity

Analyzing

Block #86,613,589

28 transactions · 24 stateful · 2026-07-09 11:24:31 UTC

Parallelism

75/100

Blocked

38%

Avg conflicts / tx

0.61

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #86,613,589  ·  28 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

10 touches
10 conflicts

0xa7013be2…c0a8

0x34b655…2a6f

8 touches
6 conflicts

0x90e113f8…c8f9

0xc8689a…ee79

6 touches
3 conflicts

0x085df2c1…305a

0x34b655…2a6f

6 touches
3 conflicts

0x4caf91f9…8ab5

0x34b655…2a6f

6 touches
3 conflicts

0x5238dcb7…e0e2

0x34b655…2a6f

6 touches
3 conflicts

0x9c7d2e4b…499b

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

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

10 conflicts on slot 0xfaef08b108…f90696

← previous block·next block →recent activity