← previous blocknext block →recent activity

Analyzing

Block #85,345,194

26 transactions · 21 stateful · 2026-07-03 14:21:37 UTC

Parallelism

88/100

Blocked

29%

Avg conflicts / tx

0.31

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #85,345,194  ·  26 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

6 touches
3 conflicts

0x1da60af2…3010

0x34b655…2a6f

4 touches
1 conflict

0x3567cb6a…088f

0x34b655…2a6f

4 touches
1 conflict

0x5a8a84f9…3079

0x34b655…2a6f

4 touches
1 conflict

0x9c173acc…8db4

0x34b655…2a6f

4 touches
1 conflict

0xa57576bb…e01f

0x34b655…2a6f

4 touches
1 conflict

0xaae6463e…bfcc

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

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

3 conflicts on slot 0xfaef08b108…f90696

← previous block·next block →recent activity