← previous blocknext block →recent activity

Analyzing

Block #85,181,328

19 transactions · 15 stateful · 2026-07-02 20:10:08 UTC

Parallelism

68/100

Blocked

60%

Avg conflicts / tx

0.89

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #85,181,328  ·  19 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

0xfaef08b1…0696

0x34b655…2a6f

10 touches
10 conflicts

0x922c7ebd…6600

0xc8689a…ee79

8 touches
6 conflicts

0x086db8fc…0024

0x34b655…2a6f

8 touches
6 conflicts

0x51a914cf…a822

0x34b655…2a6f

8 touches
6 conflicts

0x548145a9…cfce

0x34b655…2a6f

8 touches
6 conflicts

0x63b15849…80b2

0x34b655…2a6f

8 touches
6 conflicts

0x74fd0a9b…3aaa

0x34b655…2a6f

8 touches
6 conflicts

0xe85c26da…af3f

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

10 conflicts on slot 0xfaef08b108…f90696

← previous block·next block →recent activity