← previous blocknext block →recent activity

Analyzing

Block #85,125,247

23 transactions · 19 stateful · 2026-07-02 13:56:23 UTC

Parallelism

70/100

Blocked

47%

Avg conflicts / tx

1.09

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #85,125,247  ·  23 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

14 touches
21 conflicts

0x922c7ebd…6600

0xc8689a…ee79

6 touches
3 conflicts

0x3230277c…ef39

0xc8689a…ee79

6 touches
3 conflicts

0x03fb27fd…0c06

0x34b655…2a6f

6 touches
3 conflicts

0x07bb3f5a…617e

0x34b655…2a6f

6 touches
3 conflicts

0x0934ec4c…50c8

0x34b655…2a6f

6 touches
3 conflicts

0x159b8597…48a4

0x34b655…2a6f

6 touches
3 conflicts

0x29f8a58c…52c6

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

21 conflicts on slot 0xfaef08b108…f90696

← previous block·next block →recent activity