← previous blocknext block →recent activity

Analyzing

Block #87,588,085

21 transactions · 19 stateful · 2026-07-14 00:00:47 UTC

Parallelism

81/100

Blocked

37%

Avg conflicts / tx

0.86

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #87,588,085  ·  21 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

0x0eeb2a30…6909

0x34b655…2a6f

8 touches
6 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

8 touches
6 conflicts

0xac2a0273…721b

0x34b655…2a6f

8 touches
6 conflicts

0x737acb78…fce8

0x34b655…2a6f

6 touches
3 conflicts

0x691e3505…dd2f

0x34b655…2a6f

6 touches
3 conflicts

0xad0c7701…1d83

0x34b655…2a6f

6 touches
3 conflicts

0x2e64e234…5cfa

0x34b655…2a6f

4 touches
1 conflict

0x2f702750…347d

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 0x0eeb2a3089…8a6909

← previous block·next block →recent activity