← previous blocknext block →recent activity

Analyzing

Block #86,657,253

21 transactions · 16 stateful · 2026-07-09 16:17:30 UTC

Parallelism

86/100

Blocked

38%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #86,657,253  ·  21 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

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0002

0x04fdea…47d7

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xce827910…ff22

0x065c9d…c394

4 touches
1 conflict

0x298ff4cf…aa9c

0x34b655…2a6f

4 touches
1 conflict

0x31d88d27…7617

0x34b655…2a6f

4 touches
1 conflict

0x4498a6fd…845a

0x34b655…2a6f

4 touches
1 conflict

0x99ecae25…abb9

0x851145…3f07

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 0x482471adbb…39122f

← previous block·next block →recent activity