← previous blocknext block →recent activity

Analyzing

Block #87,751,376

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

Parallelism

88/100

Blocked

29%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #87,751,376  ·  24 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

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x5f5a0edf…ebcc

0x34b655…2a6f

6 touches
3 conflicts

0x737acb78…fce8

0x34b655…2a6f

6 touches
3 conflicts

0x35b0198e…3e0d

0x34b655…2a6f

4 touches
1 conflict

0x4acbdbcf…a8c6

0x34b655…2a6f

4 touches
1 conflict

0x6fe7d366…78ff

0x34b655…2a6f

4 touches
1 conflict

0x74387787…5b22

0x34b655…2a6f

4 touches
1 conflict

0x747f609d…1555

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

3 conflicts on slot 0xac2a02739b…81721b

← previous block·next block →recent activity