← previous blocknext block →recent activity

Analyzing

Block #87,661,555

24 transactions · 18 stateful · 2026-07-14 08:11:56 UTC

Parallelism

83/100

Blocked

39%

Avg conflicts / tx

0.46

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

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

0x0733be30…112f

0x34b655…2a6f

6 touches
3 conflicts

0x0a6c31fc…f4c3

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0x8f825eeb…9942

0x851145…3f07

6 touches
3 conflicts

0xf8ceaa24…6e8e

0x851145…3f07

4 touches
1 conflict

0xf7640726…19a2

0x2a68ba…90c5

4 touches
1 conflict

0x19caa5cc…17c7

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 0x0733be30d6…38112f

← previous block·next block →recent activity