← previous blocknext block →recent activity

Analyzing

Block #85,906,373

13 transactions · 9 stateful · 2026-07-06 04:39:50 UTC

Parallelism

77/100

Blocked

22%

Avg conflicts / tx

0.23

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #85,906,373  ·  13 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

0xd3414a4a…b17f

0x34b655…2a6f

6 touches
3 conflicts

0xffb8950c…23c6

0x34b655…2a6f

4 touches
1 conflict

0x7506443a…4820

0x34b655…2a6f

4 touches
1 conflict

0x8ee6053a…5be3

0x34b655…2a6f

4 touches
1 conflict

0x921b0818…fd01

0x34b655…2a6f

4 touches
1 conflict

0xd01910c9…9418

0x34b655…2a6f

4 touches
1 conflict

0xd58b9a66…1c23

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

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 0xd3414a4a7f…4cb17f

← previous block·next block →recent activity