← previous blocknext block →recent activity

Analyzing

Block #87,735,361

18 transactions · 17 stateful · 2026-07-14 16:25:50 UTC

Parallelism

72/100

Blocked

47%

Avg conflicts / tx

1

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,735,361  ·  18 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

0x7e5ea60a…c4aa

0x34b655…2a6f

10 touches
10 conflicts

0x0733be30…112f

0x34b655…2a6f

8 touches
6 conflicts

0xa3a621f8…75a2

0x34b655…2a6f

6 touches
3 conflicts

0xe3ce81c6…d48d

0x34b655…2a6f

6 touches
3 conflicts

0xf3d10975…0d07

0x34b655…2a6f

6 touches
3 conflicts

0xa09be165…16b9

0x34b655…2a6f

6 touches
3 conflicts

0x9001f549…089d

0x34b655…2a6f

6 touches
3 conflicts

0x889d5e90…929a

0x2a68ba…90c5

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 0x7e5ea60ab2…b0c4aa

← previous block·next block →recent activity