← previous blocknext block →recent activity

Analyzing

Block #87,661,610

24 transactions · 21 stateful · 2026-07-14 08:12:18 UTC

Parallelism

83/100

Blocked

38%

Avg conflicts / tx

0.63

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #87,661,610  ·  24 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

0x0733be30…112f

0x34b655…2a6f

8 touches
6 conflicts

0xe6bc2816…1787

0x34b655…2a6f

6 touches
3 conflicts

0x212c5b04…5f01

0x34b655…2a6f

6 touches
3 conflicts

0x8bf661cb…bcd2

0x34b655…2a6f

6 touches
3 conflicts

0x41d9a134…ccfe

0x34b655…2a6f

4 touches
1 conflict

0x454cdf57…aebc

0x34b655…2a6f

4 touches
1 conflict

0x560b6fd9…a104

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

← previous block·next block →recent activity