← previous blocknext block →recent activity

Analyzing

Block #86,674,046

22 transactions · 20 stateful · 2026-07-09 18:09:35 UTC

Parallelism

77/100

Blocked

35%

Avg conflicts / tx

0.41

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #86,674,046  ·  22 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

0xf1345bef…5530

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x56b5f5c0…a3ad

0x34b655…2a6f

6 touches
3 conflicts

0x0dd29361…9c39

0x34b655…2a6f

4 touches
1 conflict

0x41b014d9…6c12

0x34b655…2a6f

4 touches
1 conflict

0x41b014d9…6c13

0x34b655…2a6f

4 touches
1 conflict

0x6d50e5d1…f983

0x34b655…2a6f

4 touches
1 conflict

0x83f3d320…fb59

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 0xf1345befeb…1b5530

← previous block·next block →recent activity