← previous blocknext block →recent activity

Analyzing

Block #85,179,058

40 transactions · 32 stateful · 2026-07-02 19:55:00 UTC

Parallelism

75/100

Blocked

66%

Avg conflicts / tx

1.98

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #85,179,058  ·  40 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

20 touches
45 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

14 touches
21 conflicts

0x5ad3280d…16bb

0x34b655…2a6f

10 touches
10 conflicts

0x6167486f…db40

0x34b655…2a6f

10 touches
10 conflicts

0x2c8bf7d9…3cc7

0xc8689a…ee79

10 touches
10 conflicts

0x3ea25e92…a36d

0x34b655…2a6f

10 touches
10 conflicts

0x8cf3d245…1d0d

0x69df8a…6292

8 touches
6 conflicts

0xb05cd4f5…73d0

0x69df8a…6292

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

45 conflicts on slot 0xfaef08b108…f90696

← previous block·next block →recent activity