← previous blocknext block →recent activity

Analyzing

Block #85,681,117

31 transactions · 19 stateful · 2026-07-05 03:38:17 UTC

Parallelism

84/100

Blocked

37%

Avg conflicts / tx

0.29

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #85,681,117  ·  31 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

0x126a0344…4465

0x34b655…2a6f

6 touches
3 conflicts

0xb4e0a934…5fc7

0x34b655…2a6f

6 touches
3 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

4 touches
1 conflict

0x01e7b865…6e6e

0x188d58…ea8e

4 touches
1 conflict

0x033cf007…136d

0x34b655…2a6f

4 touches
1 conflict

0x085df2c1…305a

0x34b655…2a6f

4 touches
1 conflict

0x171ff85b…255e

0x34b655…2a6f

4 touches
1 conflict

0x2877f440…c2c8

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 0x126a0344b1…d04465

← previous block·next block →recent activity