← previous blocknext block →recent activity

Analyzing

Block #85,125,089

25 transactions · 19 stateful · 2026-07-02 13:55:19 UTC

Parallelism

80/100

Blocked

37%

Avg conflicts / tx

0.52

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #85,125,089  ·  25 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

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

6 touches
3 conflicts

0x11431f9d…42c5

0x34b655…2a6f

4 touches
1 conflict

0x159b8597…48a4

0x34b655…2a6f

4 touches
1 conflict

0x22d3c767…e4d1

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x562f98b6…7c17

0x34b655…2a6f

4 touches
1 conflict

0x79b3209b…f766

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

10 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity