← previous blocknext block →recent activity

Analyzing

Block #85,544,742

25 transactions · 17 stateful · 2026-07-04 12:30:18 UTC

Parallelism

80/100

Blocked

41%

Avg conflicts / tx

0.52

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #85,544,742  ·  25 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x2c8bf7d9…3cc7

0xc8689a…ee79

6 touches
3 conflicts

0x1ed8510f…3610

0x34b655…2a6f

6 touches
3 conflicts

0x54b193ad…c830

0x34b655…2a6f

6 touches
3 conflicts

0x7b3da897…b268

0x34b655…2a6f

6 touches
3 conflicts

0x7cb2f3fa…4836

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0xbfca3cd0…5023

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