← previous blocknext block →recent activity

Analyzing

Block #87,628,757

26 transactions · 22 stateful · 2026-07-14 04:32:49 UTC

Parallelism

73/100

Blocked

36%

Avg conflicts / tx

0.96

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #87,628,757  ·  26 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

0x08330b36…ae29

0x34b655…2a6f

12 touches
15 conflicts

0xea02471d…1542

0x34b655…2a6f

8 touches
6 conflicts

0xf3d10975…0d07

0x34b655…2a6f

8 touches
6 conflicts

0x5b145de0…367c

0xc8689a…ee79

6 touches
3 conflicts

0x49f75237…44f4

0x34b655…2a6f

6 touches
3 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0x9599eb41…b5d6

0x34b655…2a6f

6 touches
3 conflicts

0xb245fe36…d765

0x34b655…2a6f

6 touches
3 conflicts

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 0x08330b3687…a7ae29

← previous block·next block →recent activity