← previous blocknext block →recent activity

Analyzing

Block #85,100,776

42 transactions · 34 stateful · 2026-07-02 11:12:25 UTC

Parallelism

71/100

Blocked

71%

Avg conflicts / tx

1.93

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #85,100,776  ·  42 txs across 12 waves  ·  depth 12
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

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

18 touches
36 conflicts

0x00000000…003d

0xa6afd3…d132

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0x664bf99e…0a8c

0x34b655…2a6f

8 touches
6 conflicts

0x2886e2bc…6ab8

0x065c9d…c394

8 touches
6 conflicts

0x731e6d82…2883

0x065c9d…c394

8 touches
6 conflicts

0x7b3da897…b268

0x34b655…2a6f

8 touches
6 conflicts

0x7cb2f3fa…4836

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

36 conflicts on slot 0xfaef08b108…f90696

← previous block·next block →recent activity