← previous blocknext block →recent activity

Analyzing

Block #85,901,299

17 transactions · 12 stateful · 2026-07-06 04:06:04 UTC

Parallelism

82/100

Blocked

17%

Avg conflicts / tx

0.18

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #85,901,299  ·  17 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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xf3d10975…0d07

0x34b655…2a6f

4 touches
1 conflict

0x59dccbd8…2bf6

0x34b655…2a6f

4 touches
1 conflict

0x6637e421…af93

0x34b655…2a6f

4 touches
1 conflict

0x673891f1…bf47

0x34b655…2a6f

4 touches
1 conflict

0x69941f7e…3b1d

0x34b655…2a6f

4 touches
1 conflict

0x89a63bb6…c2b5

0x34b655…2a6f

4 touches
1 conflict

0xbc04d98e…a484

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