← previous blocknext block →recent activity

Analyzing

Block #85,856,084

24 transactions · 19 stateful · 2026-07-05 23:04:56 UTC

Parallelism

83/100

Blocked

37%

Avg conflicts / tx

0.38

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #85,856,084  ·  24 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

0xd99b3b64…1c95

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xafd867b7…2b2d

0x34b655…2a6f

4 touches
1 conflict

0xafd867b7…2b2e

0x34b655…2a6f

4 touches
1 conflict

0x160f117d…8e90

0x065c9d…c394

4 touches
1 conflict

0x00000000…0002

0x04fdea…47d7

4 touches
1 conflict

0x649c1759…9b83

0x34b655…2a6f

3 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 0xd99b3b6441…7a1c95

← previous block·next block →recent activity