← previous blocknext block →recent activity

Analyzing

Block #85,129,862

24 transactions · 23 stateful · 2026-07-02 14:27:14 UTC

Parallelism

79/100

Blocked

35%

Avg conflicts / tx

0.5

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #85,129,862  ·  24 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

0xec0e0220…cb90

0x34b655…2a6f

6 touches
3 conflicts

0x21f3627e…adb0

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…00c9

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad07

0x34b655…2a6f

6 touches
3 conflicts

0xffb8950c…23c6

0x34b655…2a6f

6 touches
3 conflicts

0x6286953c…1cdf

0x34b655…2a6f

6 touches
3 conflicts

0xfaef08b1…0696

0x34b655…2a6f

6 touches
3 conflicts

0xbd7b2332…68aa

0xd32edf…ff58

5 touches
3 conflicts

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 0xec0e022022…becb90

← previous block·next block →recent activity