← previous blocknext block →recent activity

Analyzing

Block #87,588,715

26 transactions · 20 stateful · 2026-07-14 00:05:00 UTC

Parallelism

81/100

Blocked

30%

Avg conflicts / tx

0.54

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,588,715  ·  26 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x22e0cc1d…ad0d

0x34b655…2a6f

10 touches
10 conflicts

0x18904470…0ef9

0x34b655…2a6f

8 touches
6 conflicts

0x105e7432…03f4

0x34b655…2a6f

6 touches
3 conflicts

0x44591918…191e

0x34b655…2a6f

6 touches
3 conflicts

0x758fd828…245c

0x34b655…2a6f

6 touches
3 conflicts

0x1d099f02…4793

0x34b655…2a6f

4 touches
1 conflict

0x1f2cd70b…94be

0x34b655…2a6f

4 touches
1 conflict

0x040d237c…b53c

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

10 conflicts on slot 0x22e0cc1d4a…90ad0d

← previous block·next block →recent activity