← previous blocknext block →recent activity

Analyzing

Block #85,923,482

23 transactions · 17 stateful · 2026-07-06 06:33:48 UTC

Parallelism

87/100

Blocked

35%

Avg conflicts / tx

0.43

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #85,923,482  ·  23 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

0x3439dfbc…0d03

0x34b655…2a6f

6 touches
3 conflicts

0xafd867b7…2b2d

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0x1c38c547…b04c

0xd32edf…ff58

5 touches
3 conflicts

0x265d35de…2f86

0x34b655…2a6f

4 touches
1 conflict

0x34d95d94…3a16

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x4a5956ef…e226

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 0x3439dfbcc6…080d03

← previous block·next block →recent activity