← previous blocknext block →recent activity

Analyzing

Block #85,138,569

21 transactions · 18 stateful · 2026-07-02 15:25:22 UTC

Parallelism

81/100

Blocked

39%

Avg conflicts / tx

0.43

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #85,138,569  ·  21 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

0x43e2eda1…396f

0x34b655…2a6f

6 touches
3 conflicts

0x25e3730b…24a9

0x34b655…2a6f

4 touches
1 conflict

0x2697123c…8526

0x34b655…2a6f

4 touches
1 conflict

0x30153288…6d46

0x34b655…2a6f

4 touches
1 conflict

0x4b5be307…0a25

0x34b655…2a6f

4 touches
1 conflict

0x51087f5a…61f7

0x34b655…2a6f

4 touches
1 conflict

0x7ffd7c99…ac51

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