← previous blocknext block →recent activity

Analyzing

Block #85,124,810

33 transactions · 20 stateful · 2026-07-02 13:53:27 UTC

Parallelism

88/100

Blocked

35%

Avg conflicts / tx

0.33

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #85,124,810  ·  33 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

0x22d3c767…e4d1

0x34b655…2a6f

6 touches
3 conflicts

0x25de453d…9573

0x34b655…2a6f

6 touches
3 conflicts

0x3a192eef…3c7f

0x34b655…2a6f

6 touches
3 conflicts

0x4f4bdabd…ffba

0x34b655…2a6f

6 touches
3 conflicts

0x2c8bf7d9…3cc7

0xc8689a…ee79

6 touches
3 conflicts

0x656bd53e…af4e

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

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

6 conflicts on slot 0xfaef08b108…f90696

← previous block·next block →recent activity