← previous blocknext block →recent activity

Analyzing

Block #85,126,245

15 transactions · 13 stateful · 2026-07-02 14:03:03 UTC

Parallelism

73/100

Blocked

54%

Avg conflicts / tx

0.67

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #85,126,245  ·  15 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

0xfaef08b1…0696

0x34b655…2a6f

8 touches
6 conflicts

0x03fb27fd…0c06

0x34b655…2a6f

8 touches
6 conflicts

0x922c7ebd…6600

0xc8689a…ee79

8 touches
6 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

8 touches
6 conflicts

0x2fc0ce78…68cc

0x34b655…2a6f

8 touches
6 conflicts

0x7523ad90…2ba5

0x34b655…2a6f

8 touches
6 conflicts

0x844b7c66…8ccc

0x34b655…2a6f

8 touches
6 conflicts

0x8e5cc690…b06b

0x34b655…2a6f

8 touches
6 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 0xfaef08b108…f90696

← previous block·next block →recent activity