← previous blocknext block →recent activity

Analyzing

Block #87,876,271

12 transactions · 12 stateful · 2026-07-15 08:08:22 UTC

Parallelism

75/100

Blocked

42%

Avg conflicts / tx

0.42

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #87,876,271  ·  12 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xf481b267…dc7d

0x34b655…2a6f

4 touches
1 conflict

0xe5bb3628…e5f1

0x34b655…2a6f

4 touches
1 conflict

0xed59b1cd…8509

0x34b655…2a6f

4 touches
1 conflict

0xf47128a0…896a

0x34b655…2a6f

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x00448010…70fb

0x34b655…2a6f

4 touches
1 conflict

0x50718952…7c75

0x34b655…2a6f

4 touches
1 conflict

0x64aaadbf…f9f3

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

1 conflict on slot 0xf481b267af…e4dc7d

← previous block·next block →recent activity