← previous blocknext block →recent activity

Analyzing

Block #85,126,726

24 transactions · 22 stateful · 2026-07-02 14:06:16 UTC

Parallelism

79/100

Blocked

32%

Avg conflicts / tx

0.54

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #85,126,726  ·  24 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

0x03fb27fd…0c06

0x34b655…2a6f

6 touches
3 conflicts

0x63da0619…7a55

0x34b655…2a6f

6 touches
3 conflicts

0x81df88ae…0e9f

0x34b655…2a6f

6 touches
3 conflicts

0x8dc11583…303d

0x34b655…2a6f

6 touches
3 conflicts

0x8e5cc690…b06b

0x34b655…2a6f

6 touches
3 conflicts

0x98592584…be76

0x34b655…2a6f

6 touches
3 conflicts

0x9f40a209…1193

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