← previous blocknext block →recent activity

Analyzing

Block #85,193,230

18 transactions · 16 stateful · 2026-07-02 21:29:19 UTC

Parallelism

61/100

Blocked

50%

Avg conflicts / tx

1

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #85,193,230  ·  18 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

10 touches
10 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

8 touches
6 conflicts

0x159b8597…48a4

0x34b655…2a6f

8 touches
6 conflicts

0xa1571d54…ae41

0x34b655…2a6f

8 touches
6 conflicts

0x7ee6007b…fd68

0x34b655…2a6f

8 touches
6 conflicts

0x922c7ebd…6600

0xc8689a…ee79

8 touches
6 conflicts

0xe727ab72…768b

0x34b655…2a6f

8 touches
6 conflicts

0x5e2f5da3…68a9

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

10 conflicts on slot 0xfaef08b108…f90696

← previous block·next block →recent activity