← previous blocknext block →recent activity

Analyzing

Block #87,878,086

27 transactions · 18 stateful · 2026-07-15 08:20:30 UTC

Parallelism

81/100

Blocked

50%

Avg conflicts / tx

0.59

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,878,086  ·  27 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x974c36fe…1cd7

0x34b655…2a6f

8 touches
6 conflicts

0x889d5e90…929a

0x2a68ba…90c5

8 touches
6 conflicts

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x0733be30…112f

0x34b655…2a6f

6 touches
3 conflicts

0x58f65aa1…8f98

0x34b655…2a6f

4 touches
1 conflict

0x64aaadbf…f9f3

0x34b655…2a6f

4 touches
1 conflict

0x6fe7d366…78ff

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 0x974c36fe03…4f1cd7

← previous block·next block →recent activity