← previous blocknext block →recent activity

Analyzing

Block #85,161,683

26 transactions · 22 stateful · 2026-07-02 17:59:18 UTC

Parallelism

81/100

Blocked

36%

Avg conflicts / tx

0.54

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #85,161,683  ·  26 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

0x6bdb9869…7558

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x4409a908…bbdd

0x34b655…2a6f

6 touches
3 conflicts

0x731e6d82…2883

0x065c9d…c394

4 touches
1 conflict

0x9676e548…754f

0x40c49f…2af0

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x2886e2bc…6ab8

0x065c9d…c394

4 touches
1 conflict

0x085df2c1…305a

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 0x6bdb9869c7…427558

← previous block·next block →recent activity