← previous blocknext block →recent activity

Analyzing

Block #86,565,268

20 transactions · 17 stateful · 2026-07-09 06:00:29 UTC

Parallelism

85/100

Blocked

35%

Avg conflicts / tx

0.45

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #86,565,268  ·  20 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

0x7a12283f…b18a

0x69df8a…6292

6 touches
3 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

6 touches
3 conflicts

0x0fde64da…aa3e

0x2a68ba…90c5

6 touches
3 conflicts

0x8d0d8061…d410

0xc8689a…ee79

6 touches
3 conflicts

0xabc6fb06…1401

0x851145…3f07

6 touches
3 conflicts

0x086f580e…090c

0x851145…3f07

6 touches
3 conflicts

0x00000000…003d

0x851145…3f07

6 touches
3 conflicts

0xd8fd2add…50fc

0x69df8a…6292

6 touches
3 conflicts

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: 0x69df8a43…506292

3 conflicts on slot 0x7a12283fc2…57b18a

← previous block·next block →recent activity