← previous blocknext block →recent activity

Analyzing

Block #85,973,070

27 transactions · 17 stateful · 2026-07-06 12:04:33 UTC

Parallelism

85/100

Blocked

41%

Avg conflicts / tx

0.41

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #85,973,070  ·  27 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x95d6e198…f79c

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xcb89a818…e7c1

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0002

0x04fdea…47d7

4 touches
1 conflict

0xd35bb5ac…3586

0x065c9d…c394

4 touches
1 conflict

0x4a11a172…dbef

0x34b655…2a6f

4 touches
1 conflict

0x6f7a92ed…5651

0x34b655…2a6f

4 touches
1 conflict

0x77ea60f4…e7ca

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 0x95d6e1989e…e0f79c

← previous block·next block →recent activity