← previous blocknext block →recent activity

Analyzing

Block #87,061,833

17 transactions · 15 stateful · 2026-07-11 13:20:44 UTC

Parallelism

76/100

Blocked

53%

Avg conflicts / tx

0.59

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #87,061,833  ·  17 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

0xfaef08b1…0696

0x34b655…2a6f

6 touches
3 conflicts

0x8a35acfb…d1ab

0xb1dbf0…c0d3

4 touches
1 conflict

0x00000000…0004

0xb1dbf0…c0d3

4 touches
1 conflict

0x13a54fa2…5ae3

0x2a68ba…90c5

4 touches
1 conflict

0x56b5f5c0…a3ad

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x8cc1393f…07fb

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0xa6afd3…d132

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

3 conflicts on slot 0xfaef08b108…f90696

← previous block·next block →recent activity