← previous blocknext block →recent activity

Analyzing

Block #87,135,538

25 transactions · 20 stateful · 2026-07-11 21:32:58 UTC

Parallelism

72/100

Blocked

50%

Avg conflicts / tx

1.08

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #87,135,538  ·  25 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

14 touches
21 conflicts

0x8a35acfb…d1ab

0xb1dbf0…c0d3

10 touches
10 conflicts

0xb835d684…089c

0x34b655…2a6f

6 touches
3 conflicts

0x8a35acfb…d1aa

0xb1dbf0…c0d3

6 touches
3 conflicts

0x64fbf9b1…60a3

0x34b655…2a6f

6 touches
3 conflicts

0xa9988419…9f45

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xe6e45a35…0627

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

21 conflicts on slot 0xfaef08b108…f90696

← previous block·next block →recent activity