← previous blocknext block →recent activity

Analyzing

Block #85,158,064

19 transactions · 18 stateful · 2026-07-02 17:35:16 UTC

Parallelism

79/100

Blocked

39%

Avg conflicts / tx

0.84

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #85,158,064  ·  19 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x22e0cc1d…ad0d

0x34b655…2a6f

8 touches
6 conflicts

0xb6ed511f…6b68

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xebda062f…e87a

0x34b655…2a6f

6 touches
3 conflicts

0xb44d5376…33cc

0x34b655…2a6f

6 touches
3 conflicts

0x63da0619…7a55

0x34b655…2a6f

6 touches
3 conflicts

0x8f102617…fd7c

0x34b655…2a6f

6 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

6 conflicts on slot 0x22e0cc1d4a…90ad0d

← previous block·next block →recent activity