← previous blocknext block →recent activity

Analyzing

Block #85,907,563

22 transactions · 18 stateful · 2026-07-06 04:47:46 UTC

Parallelism

82/100

Blocked

39%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #85,907,563  ·  22 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

0xafd867b7…2b2e

0x34b655…2a6f

6 touches
3 conflicts

0xafd867b7…2b2d

0x34b655…2a6f

6 touches
3 conflicts

0xfba04a46…7470

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x3cf50d44…961b

0x34b655…2a6f

4 touches
1 conflict

0x677077cf…1de6

0x34b655…2a6f

4 touches
1 conflict

0x921b0818…fd01

0x34b655…2a6f

4 touches
1 conflict

0xb2fa1675…4e07

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 0xafd867b7ed…d92b2e

← previous block·next block →recent activity