← previous blocknext block →recent activity

Analyzing

Block #85,614,954

21 transactions · 18 stateful · 2026-07-04 20:17:53 UTC

Parallelism

71/100

Blocked

44%

Avg conflicts / tx

0.52

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #85,614,954  ·  21 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

6 touches
3 conflicts

0x957c875f…b3f9

0x34b655…2a6f

6 touches
3 conflicts

0x08e8f2c9…a11a

0x34b655…2a6f

4 touches
1 conflict

0x178db37f…debb

0x34b655…2a6f

4 touches
1 conflict

0x2bde601f…00eb

0x34b655…2a6f

4 touches
1 conflict

0x33b9b421…f42c

0x34b655…2a6f

4 touches
1 conflict

0x5fe7e126…6dd2

0x34b655…2a6f

4 touches
1 conflict

0x69c73062…a10b

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity