← previous blocknext block →recent activity

Analyzing

Block #86,963,637

24 transactions · 21 stateful · 2026-07-11 02:24:40 UTC

Parallelism

83/100

Blocked

33%

Avg conflicts / tx

0.46

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,963,637  ·  24 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

0xb652c396…b8fa

0x34b655…2a6f

8 touches
6 conflicts

0xb1e4ea6c…3e29

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0xfaef08b1…0696

0x34b655…2a6f

6 touches
3 conflicts

0x8a35acfb…d1ac

0xb1dbf0…c0d3

6 touches
3 conflicts

0x8a35acfb…d1ad

0xb1dbf0…c0d3

5 touches
3 conflicts

0x35d95fb0…db9e

0x34b655…2a6f

4 touches
1 conflict

0x35d95fb0…db9f

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 0xb652c39667…34b8fa

← previous block·next block →recent activity