← previous blocknext block →recent activity

Analyzing

Block #87,760,496

14 transactions · 13 stateful · 2026-07-14 19:13:57 UTC

Parallelism

79/100

Blocked

31%

Avg conflicts / tx

0.5

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #87,760,496  ·  14 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

0xf3d10975…0d07

0x34b655…2a6f

6 touches
3 conflicts

0x0733be30…112f

0x34b655…2a6f

4 touches
1 conflict

0x085df2c1…305a

0x34b655…2a6f

4 touches
1 conflict

0x2625753b…ac16

0x34b655…2a6f

4 touches
1 conflict

0x2fdfe038…c16c

0x34b655…2a6f

4 touches
1 conflict

0x49e0713b…0e69

0x34b655…2a6f

4 touches
1 conflict

0x53b4ef2b…8a05

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

3 conflicts on slot 0xf3d10975b0…050d07

← previous block·next block →recent activity