← previous blocknext block →recent activity

Analyzing

Block #85,906,973

21 transactions · 17 stateful · 2026-07-06 04:43:50 UTC

Parallelism

76/100

Blocked

41%

Avg conflicts / tx

0.43

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #85,906,973  ·  21 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xf1345bef…5530

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x40c49f…2af0

4 touches
1 conflict

0x342fbbca…d443

0x40c49f…2af0

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0xec7d120d…7084

0x34b655…2a6f

4 touches
1 conflict

0x427d1120…4eb1

0x34b655…2a6f

4 touches
1 conflict

0x6f900be0…cd6e

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity