← previous blocknext block →recent activity

Analyzing

Block #87,734,751

25 transactions · 24 stateful · 2026-07-14 16:21:45 UTC

Parallelism

72/100

Blocked

29%

Avg conflicts / tx

0.76

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #87,734,751  ·  25 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

12 touches
15 conflicts

0xcf5ef070…7d4f

0x34b655…2a6f

8 touches
6 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

8 touches
6 conflicts

0x53355553…2976

0x34b655…2a6f

6 touches
3 conflicts

0x387231f6…6b29

0x34b655…2a6f

4 touches
1 conflict

0x38e39eef…50bd

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x5d0a87fc…c5e4

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

15 conflicts on slot 0x0733be30d6…38112f

← previous block·next block →recent activity