← previous blocknext block →recent activity

Analyzing

Block #86,960,009

22 transactions · 17 stateful · 2026-07-11 02:00:24 UTC

Parallelism

73/100

Blocked

53%

Avg conflicts / tx

0.73

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #86,960,009  ·  22 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x4681609f…6493

0x34b655…2a6f

8 touches
6 conflicts

0x914175c3…5909

0xd32edf…ff58

7 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x2036b9cd…f20d

0x065c9d…c394

4 touches
1 conflict

0x16a8cd0c…27bd

0x34b655…2a6f

4 touches
1 conflict

0x21002368…91f4

0x34b655…2a6f

4 touches
1 conflict

0x28c180e1…f1e2

0x34b655…2a6f

4 touches
1 conflict

0x3347cbe5…846c

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

6 conflicts on slot 0x4681609fd4…e96493

← previous block·next block →recent activity