← previous blocknext block →recent activity

Analyzing

Block #86,709,500

19 transactions · 18 stateful · 2026-07-09 22:06:08 UTC

Parallelism

79/100

Blocked

39%

Avg conflicts / tx

0.42

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,709,500  ·  19 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

0x06aed19e…ca57

0x34b655…2a6f

4 touches
1 conflict

0x09500602…94e9

0x34b655…2a6f

4 touches
1 conflict

0x14b821e0…6edf

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x3ccc3d17…de83

0x34b655…2a6f

4 touches
1 conflict

0x4556b467…a487

0x34b655…2a6f

4 touches
1 conflict

0x48fb2063…4025

0x34b655…2a6f

4 touches
1 conflict

0x548145a9…cfce

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

1 conflict on slot 0x06aed19eee…1cca57

← previous block·next block →recent activity