← previous blocknext block →recent activity

Analyzing

Block #87,734,914

23 transactions · 22 stateful · 2026-07-14 16:22:51 UTC

Parallelism

83/100

Blocked

32%

Avg conflicts / tx

0.57

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #87,734,914  ·  23 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

0x0dd44476…ef40

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…00c9

0x34b655…2a6f

6 touches
3 conflicts

0x4e3a7822…a8c5

0x34b655…2a6f

4 touches
1 conflict

0x738f1a94…ed05

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4a2

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4a4

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4ab

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 0x0dd44476b8…7fef40

← previous block·next block →recent activity