← previous blocknext block →recent activity

Analyzing

Block #85,930,639

24 transactions · 20 stateful · 2026-07-06 07:21:31 UTC

Parallelism

88/100

Blocked

30%

Avg conflicts / tx

0.29

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #85,930,639  ·  24 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

0xe5bb3628…e5f1

0x34b655…2a6f

6 touches
3 conflicts

0x7aad02c6…b979

0x34b655…2a6f

6 touches
3 conflicts

0x160f117d…8e90

0x065c9d…c394

4 touches
1 conflict

0x994e8297…56b6

0x065c9d…c394

4 touches
1 conflict

0x13a54fa2…5ae3

0x2a68ba…90c5

4 touches
1 conflict

0x1aaf4996…65ec

0x34b655…2a6f

4 touches
1 conflict

0x68c07cb9…ae14

0x34b655…2a6f

4 touches
1 conflict

0x7fa509a2…3ec9

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 0xe5bb3628b5…71e5f1

← previous block·next block →recent activity