← previous blocknext block →recent activity

Analyzing

Block #85,147,124

21 transactions · 18 stateful · 2026-07-02 16:22:26 UTC

Parallelism

71/100

Blocked

44%

Avg conflicts / tx

0.9

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #85,147,124  ·  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

0xfaef08b1…0696

0x34b655…2a6f

12 touches
15 conflicts

0x922c7ebd…6600

0xc8689a…ee79

6 touches
3 conflicts

0x264f7d7d…8444

0x34b655…2a6f

6 touches
3 conflicts

0x47579483…bda8

0x34b655…2a6f

6 touches
3 conflicts

0x548145a9…cfce

0x34b655…2a6f

6 touches
3 conflicts

0x5b353877…605d

0x34b655…2a6f

6 touches
3 conflicts

0x63b15849…80b2

0x34b655…2a6f

6 touches
3 conflicts

0x7506443a…4820

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

15 conflicts on slot 0xfaef08b108…f90696

← previous block·next block →recent activity