← previous blocknext block →recent activity

Analyzing

Block #86,956,730

21 transactions · 20 stateful · 2026-07-11 01:38:29 UTC

Parallelism

81/100

Blocked

35%

Avg conflicts / tx

0.52

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,956,730  ·  21 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

0x7e5ea60a…c4aa

0x34b655…2a6f

8 touches
6 conflicts

0x92385428…6941

0x34b655…2a6f

8 touches
6 conflicts

0x8a35acfb…d1ac

0xb1dbf0…c0d3

6 touches
3 conflicts

0x8a35acfb…d1ad

0xb1dbf0…c0d3

6 touches
3 conflicts

0x6c7e1952…d9c9

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x40c49f…2af0

4 touches
1 conflict

0x4363982d…e743

0x40c49f…2af0

4 touches
1 conflict

0x9d1bb389…c7d9

0xb1dbf0…c0d3

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 0x7e5ea60ab2…b0c4aa

← previous block·next block →recent activity