← previous blocknext block →recent activity

Analyzing

Block #86,779,017

16 transactions · 15 stateful · 2026-07-10 05:50:34 UTC

Parallelism

75/100

Blocked

47%

Avg conflicts / tx

0.69

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,779,017  ·  16 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

0xf9e23360…8ef7

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x0733be30…112f

0x34b655…2a6f

6 touches
3 conflicts

0x7d9ee4ce…cf7e

0xd32edf…ff58

5 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x4e66a473…9fe8

0x34b655…2a6f

4 touches
1 conflict

0x7754e0f5…d02e

0x34b655…2a6f

4 touches
1 conflict

0x1d84bebc…07d0

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 0xf9e23360ff…e88ef7

← previous block·next block →recent activity